-
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
Breaking API change for azurerm_application_insights_web_test
- now returns a 201
#16805
Comments
Related to Azure/azure-sdk-for-go#2465 @jhendrixMSFT FYI |
Same here! Started to fail on the 201 since last saturday. After that upgraded to TerraForm 1.1.9 and Azure RM Provider 3.6, but is still complaining: insights.WebTestsClient#CreateOrUpdate: Failure responding to request: StatusCode=201 -- Original Error: autorest/azure: Service returned an error. Status=201 Code="Unknown" Message="Unknown service error" |
Started to fail on the 201 since last Thursday(May 12th 2022). we are using TerraForm 0.14.11 and Azure RM Provider 3.6, but complaining with : insights.WebTestsClient#CreateOrUpdate: Failure responding to request: StatusCode=201 -- Original Error: autorest/azure: Service returned an error. Status=201 Code="Unknown" Message="Unknown service error" |
We're seeing the same behaviour for the |
Note that this appears to be intermittent. Sometimes despite the 201, the resource is created and the provider will happily succeed. In other instances, it does not and terminates with a failure. In case of a failure, a retry/re-apply will result in another error because the resource will have been created by then but terraform does not know about it (not in state). |
We are experiencing the same issue with azurerm_application_insights_web_test resource. The web test is created but the run fails because the API call returns 201 and not 200. The proposed workaround - re-running the script - does not work unless I manually update the state. Terraform attempts to update the web test again. Here is the exact call (anonymized) that fails with Terraform traces set to debug:
According to the Microsoft documentation the used API should return 200: |
Worth noting that this appears to be MS updating their API but not the SDK issue. |
@vap78 thanks for the debug logs, I've opened this upstream PR which'll fix this in the SDK. |
azurerm_monitor_scheduled_query_rules_alert
create/update fails azurerm_application_insights_web_test
- now returns a 201
Based on our Acceptance Tests it appears the upstream API bug has been reverted - can anyone confirm if this is still an issue for them (and if so, in which region)? Thanks! |
It is currently working for me, given that it worked already sporadically before not sure how reliable that is. I reached out the the responsible parties internally and shared the link to this issue - waiting for a response. |
Workaround on our side: #16845 Whilst the API does appear to have been reverted, since the upstream Swagger PR hasn't been merged yet, we're using a fork of the Azure SDK client there rather than the official SDK, but we can switch back if/when that's merged. |
It is also working on our side! Tnx!!! |
Can confirm that it works for region West Europe. Thanks! |
This functionality has been released in v3.7.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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.1.9
AzureRM Provider Version
3.5.0
Affected Resource(s)/Data Source(s)
azurerm_monitor_scheduled_query_rules_alert
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
This should successfully create an AppInsights Availability test. This is the case - but the creation causes an error and fails the
terraform apply
run.Actual Behaviour
The execution of
terraform apply
fails creating this resource.Steps to Reproduce
No response
Important Factoids
No response
References
The text was updated successfully, but these errors were encountered: