Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v2 apps encounter 409 CONFLICT from associated Storage Account #430

Closed
brandonh-msft opened this issue Sep 5, 2018 · 6 comments
Closed

Comments

@brandonh-msft
Copy link
Member

brandonh-msft commented Sep 5, 2018

nupkg v1.6.0

Created a Function App from scratch w/ an associated storage account, all is well here.
I deploy my v2 Function App from Visual Studio 2017. Incidentally I also deployed identical code to a v1 Function app.

In the V2 Function App, the App Insights Live Stream shows me continuous 409 CONFLICT errors coming from the Storage Account:

image

The v1 Function App has no such issue and it's worth noting that the v1.5.0 nupkg didn't have this issue.

@cgillum
Copy link
Member

cgillum commented Sep 5, 2018

Some questions:

  • One possibility is that there is a regression caused by the recent Azure Functions v2 update. Have you seen this in any non-durable functions apps?
  • Is there any way to get more information on these 429s? I expect 429 may have different meanings depending on the context.

@brandonh-msft
Copy link
Member Author

Answers:

  1. I haven't tried yet but can quickly spin up a v2 app and run it. However they don't interact w/ Storage in the same way, so...
  2. I'll dig in to App Insights' logs and get more details on a few of them & post back. standby.

@brandonh-msft
Copy link
Member Author

I get some 404s on a standard Function App. Just created an HTTP Trigger one from w/in the portal and hit it a few times:

image

Still working on pulling out details from AI on the DF runs; for whatever reason my AI Events, Metrics, and Failures are all completely blank 😟

@brandonh-msft
Copy link
Member Author

brandonh-msft commented Sep 5, 2018

Unfortunately for whatever reason my AI instance proper is reporting zero data w/in it (have contacted the AI team). Perhaps something due to the current outage?

Regardless, kicked off the DF one again and saw the 409s and even a 412:

image

@brandonh-msft
Copy link
Member Author

brandonh-msft commented Sep 5, 2018

this has been reported by other users here and is now being tracked here

looks to be related to the breaking change to v2. closing.

@cgillum
Copy link
Member

cgillum commented Sep 5, 2018

Cool. Thanks for confirming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants