Error details Error details ResourceInUnupdatableState Target Spark pool specified in Spark job definition is not in succeeded state. Current state: Provisioning
Was doing deployment of spark spool thorugh CICD for synapse. Failure happened and keep saying the spool is in Provisioning state
-
Manoj Kumar Boyini 17,060 Reputation points • Microsoft External Staff • Moderator
Hi Johnny Lam,
Check for provisioning delays or failuresIf the pool stays stuck in “Provisioning” for a long time, verify that you’re not hitting subscription or regional quotas, and check Azure Service Health for any ongoing issues.
Sometimes custom libraries can slow or block pool creation. If you recently added packages, try removing them to see if the pool can finish provisioning.
Sign in to comment
1 answer
-
Smaran Thoomu 35,375 Reputation points • Microsoft External Staff • Moderator
Hi @Johnny Lam It looks like your CI/CD deployment is trying to push artifacts (like a notebook or pipeline) that reference a Spark pool before that pool has finished provisioning. When ARM or your CI/CD engine sees the pool’s provisioningState still at “Provisioning,” any subresources that target it can’t be updated or created, hence the ResourceInUnupdatableState error.
Here’s what you can do:
- Wait for the pool to finish provisioning before deploying downstream artifacts
- If you’re using Azure CLI in your pipeline, add a step after creating/updating the Spark pool:
This command will block until the pool’s provisioningState transitions to “Succeeded.”az synapse spark pool wait \ --workspace-name <yourWorkspace> \ --name <yourSparkPool> \ --updated
- If you’re using Azure CLI in your pipeline, add a step after creating/updating the Spark pool:
- Leverage dependsOn in your ARM templates
- Make sure your job definition or notebook resource in the ARM template has a
dependsOnentry pointing to the Spark pool resource. That way, ARM knows to fully finish creating the pool before trying to deploy anything that references it.
- Make sure your job definition or notebook resource in the ARM template has a
- Check for provisioning delays or failures
- If the pool stays stuck in “Provisioning” for a long time, verify that you’re not hitting subscription or regional quotas, and check Azure Service Health for any ongoing issues.
- Sometimes custom libraries can slow or block pool creation. If you recently added packages, try removing them to see if the pool can finish provisioning.
After adding the wait or proper dependency, your artifacts should deploy cleanly once the pool is in a “Succeeded” state. Hope that helps!
References:
- Wait for the pool to finish provisioning before deploying downstream artifacts
