-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
service unavailable while azurerm_api_management_api updates api definition #22973
Comments
@mrickly thanks for opening this issue. Could you explain that "the service cannot be reached" what exactly are the symptoms? Also, is it possible to provide a complete tf configuration (including variable values) and repro steps to help reproduce/troubleshoot? |
Hello @sinbai , thank you for reaching out! "the service cannot be reached" means for instance that we get a 500 response every time we try to call one of the api endpoints from the developer portal. After 30 seconds, the unavailability goes away (200 response again). It cannot be reached by another service deployed on our AKS cluster either. What I could offer right now is to provide a commented extract (only 280 lines in total) from the TRACE level log of the provider, which shows exactly what happens. I believe that it would be the most useful to you. Basically, it shows that the module updates the api without specifying the |
@sinbai : Thank you very much for acknowledging the issue and providing a fix so rapidly! I am subscribed to both this issue and your pull request. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Is there an existing issue for this?
Community Note
Terraform Version
1.5.4
AzureRM Provider Version
3.65.0
Affected Resource(s)/Data Source(s)
azurerm_api_management_api
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
The terraform apply should complete within seconds. No service interruption should be observed.
Actual Behaviour
As can be seen from the log extract (only relevant part, this is a deployment with other things happening), the execution takes 31 seconds. During this time, the service cannot be reached. Note that this happens only if the api definition (openapi description) is modified. Hence it is not related to the availability of backend pods.
Steps to Reproduce
No response
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: