Open aristosvo opened 2 years ago
@ericshape do you know which team I should contact for this issue?
@aristosvo for these online service issues which impact your SLOs, I suggest contacting Azure Support and issuing an IcM ticket. Github API repo is not a good channel to provide Azure supports immedately. Our Azure supports are 24X7.
@ericshape I am not looking for support, at least not that I was aware of, these are issues which I faced during tests for the Terraform Provider for Azure.
I don't have a subscription which I can use with (paid) support for the community work I'm doing unfortunately, so if that's the way there is no channel for me to report these.
I guess the error message provides hints {"code":"40802","message":"A service objective assignment on server \u0027acctestsqlserver211129104546431506\u0027 and database \u0027acctestdb211129104546431506\u0027 is already in progress. Please wait until the service objective assignment state for the database is marked as \u0027Completed\u0027.","target":null,"details":[{"code":"40802","message":"A service objective assignment on server \u0027acctestsqlserver211129104546431506\u0027 and database \u0027acctestdb211129104546431506\u0027 is already in progress. Please wait until the service objective assignment state for the database is marked as \u0027Completed\u0027.","target":null,"severity":"16"}],"innererror":[]}
The object assignment is in progress.
@ericshape True, but this is caused by the action which went timeout just before. This timeout is crucial in this behavior, as it still acts on the resource but feedback isn't given.
It's impossible to code against an API which has such behavior, and as such needs a fix. The problem is not the final error, but the GatewayTimeout just before.
@aristosvo I have created an internal support ticket to track it. please send me (ji dot wang A_T_symbol microsoft_dot_com) your email and I can let you in the loop.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
Author: | aristosvo |
---|---|
Assignees: | - |
Labels: | `SQL`, `Service Attention` |
Milestone: | - |
@azureSQLGitHub When trying to switch Zone Redundancy a SQL database with package version 2017-03-01-preview of the Microsoft.Sql API, GatewayTimeouts are showing up:
It seems the time-out is triggering some action which blocks subsequent requests. GatewayTimeout is usually an indicator of bad error handling server side.
Linked issues
azurerm
, which can be triggered by runninggit clone https://github.com/hashicorp/terraform-provider-azurerm.git && cd terraform-provider-azurerm && go install && make acctests SERVICE='sql' TESTARGS='-run=TestAccSqlDatabase_zoneRedundant'