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

[Azure Kusto] : Parallel Create Kusto database script error #18845

Open
sinbai opened this issue Apr 28, 2022 · 4 comments
Open

[Azure Kusto] : Parallel Create Kusto database script error #18845

sinbai opened this issue Apr 28, 2022 · 4 comments
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@sinbai
Copy link

sinbai commented Apr 28, 2022

When creating multiple Kusto database scripts programmatically in parallel by Create Kusto Script API, and calling azure-asyncoperation API to get provisioningState, the following error occurs.

"error":{"code":"ServiceIsInMaintenance","message":"[Conflict] Cluster 'acctestkc' is in process of maintenance for a short period. You may retry to invoke the operation in a few minutes."}

Repro Steps:

  1. Create a Kusto database script "test01" by Create Kusto Script API.
  2. Create a Kusto database script "test02" by Create Kusto Script API.
  3. Call azure-asyncoperation API to obtain the provisioningState of script "test01".
  4. Call azure-asyncoperation API to obtain the provisioningState of script "test02". => got above error

Expected: Scripts "test001" and "test002" could be created successfully.
Actual: Script "test001" was created successfully, script "test002" failed to be created.

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Apr 28, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 7, 2022
@SatishBoddu-MSFT SatishBoddu-MSFT added Service Attention Workflow: This issue is responsible by Azure service team. and removed CXP Attention labels May 17, 2022
@mojanas
Copy link

mojanas commented Jul 25, 2022

Hey all - author of the terraform issue above here - I believe this issue is now resolved in terraform but is still present for those using Bicep. Any update on fixing the bug at the service level? This is blocking the creation of tables (via the scripts) for multiple databases on the same cluster.

@sonphnt
Copy link

sonphnt commented Apr 25, 2023

This has been 1 year since the ticket was created. I have the same with multiple databases and table deployments now with bicep. Have we fixed this for bicep or is there any way to make it work? Thanks.

@apalich
Copy link

apalich commented Aug 16, 2023

Is it fixed yet, getting same error when trying add multiple managed private endpoints.

  • The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'. (Code: ResourceDeploymentFailure)
    • [Conflict] Cluster 'adxiacdecac' is in process of maintenance for a short period. You may retry to invoke the operation in a few minutes. (Code:ServiceIsInMaintenance)

@HassanBadir
Copy link
Contributor

same, this is really an essential simple task, need this to loop through tables instead of duplicating code, can this be fixed in Bicep like in terraform please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

7 participants