Open stweb1963 opened 3 months ago
This is very repeatable and frustrating
We have encountered this 5 times this week Setting a 'dummy' tag returns the provisioningState to 'Succeeded' which allows us to redeploy the exact same delivery with a success
Thankfully we do not have to delete the entire deployment as we would end up with new IPs which would have created a number of followup issues
The tag issue seems to work. Might have to tag more than once but it kicks the environment update off again.
@stweb1963 could you please email your details to "Azure Container Apps Support" acasupport@microsoft.com so we can check why it failed? Normal if the update of an existing environment failed, retry always help.
This issue is a: (mark with an x)
Issue description
When we redeploy the App Environment to change the number of Workload Profile instances the deployment fails with
There is no 'Proper' / 'Documented' procedure to reset the environment once in this state.
BUT
We wait about 5 minutes after the failed deployment and then set a 'Dummy' tag to anything This triggers the Container App environment to reevaluate and return to a Provisioned state This also completes the instance change of the Workload instances
Once this is complete, we redeploy our pipeline delivery and it is 100% successful
Steps to reproduce
Expected behavior [What you expected to happen.]
The deployment / Instance change will work as expected
Actual behavior [What actually happened.]
THe deployment fails
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Ex. Did this issue occur in the CLI or the Portal?
We only use Azure DevOps, Never use the portal