-
Notifications
You must be signed in to change notification settings - Fork 202
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
[BUG] Publisher is failing with "409. Content is '{"error":{"code":"PessimisticConcurrencyConflict","message":"Operation on the API is in progress","details":null}}'" When publishing on an already published APIM #141
Comments
Thanks for raising this. Is this an intermittent issue, or are you able to reproduce it consistently? If so, can you please detail reproduction steps? |
It is a recurring issue. Here is what I did:
|
Thanks. A couple of small checks:
If both are true, would you mind sharing your repo contents + the bicep file in a private repo for troubleshooting? I understand there might be some privacy concerns, so please obfuscate/delete anything you're uncomfortable sharing. |
Yes. I did a full cleanup of the repo files after upgrading to v2
Yes. The file has been modified and lint-ed to verify its validity. I added you to this repo where you can find files that I hope can help you resolve the issue https://github.com/Gabriel123N/issue-apiops-141 |
So, one thing jumps out at me. I see in the failure that it's doing a put request against That URL indicates that it's doing a PUT request against an API called Would you mind uploading the full publisher logs in the private repo? Also, please upload your |
I added the pipeline logs at the root of the repo. The configuration file is also present directly under the "apim" folder. |
I believe I've identified the issue. Working on a fix now. |
@Gabriel123N - pushed a fix in the |
I ran the pipeline a few times in a row by reproducing the steps in 2nd comment and no errors were triggered. Thank you a lot for your help once more! |
Can we close this issue? |
Yes. I wanted to leave it open a bit more in case it would suddenly appears again. But so far so good. |
Glad it's working now. Please feel free to reopen the issue if it reappears or create a new one if there's anything else. Thanks for the extensive testing! |
@guythetechie @waelkdouh I've done a similar setup with other API version sets w/ 2 versions without issue. For some reason this one refuses to publish..is there something I'm missing? Shouldn't it be able to do both API versions at once? Here's the latest pipeline logs:
|
Hi @guythetechie @waelkdouh , I'm facing this issue with v4.10.0 Publisher. Can we reopen this ticket ? This is happening whenever I run the publisher using all-artifacts, it always throw this error in PUT API operation.
|
closing due to inactivity. |
Release version
v2
Describe the bug
When deploying the publisher for a second time, the pipeline is failing with the following error at several points:
The APIM also becomes unresponsive after the failed pipeline (Management API becomes unreachable)
After deleting all APIs and attempting publish the configuration again, the pipeline completes with no issue.
Expected behavior
No 409 error are triggered when the pipeline is running against an APIM that was configured by the pipeline in the past
Actual behavior
It is not possible to publish changes to some APIs due to error HTTP error 409
Reproduction Steps
None
A rough summary of the APIM instance can be found here #135 (comment)The text was updated successfully, but these errors were encountered: