The container group is still transitioning, please retry later.

Question

The container group is still transitioning, please retry later.

34631689 10

Hi,

This morning I'm unable to start my container, any attempt fails with the error message : "The container group is still transitioning, please retry later."

But the status of the instance in the portal is "Succeeded" and the container has the status "Terminated" so I don't get it.

Does anyone have any clue?

Luca Maurelli 30 Reputation points

2023-09-25T13:50:24.0066667+00:00

I have the same issue in regione europe_west after some infrastructure problem related to a fiber-cut. I am not able to troubleshoot the problem, to date I keep restarting the container when that happens, while trying to figure out if it is related to me or to Azure. Let me know if you resolve, please.
Ivan Bicalho 0 Reputation points

2023-09-25T22:24:19.3433333+00:00

Same here, not sure what's going on, looks like something with Azure, everything was working fine so far.

2 answers

Your answer

Luca Maurelli 30 Reputation points

2023-09-25T13:50:24.0066667+00:00

I have the same issue in regione europe_west after some infrastructure problem related to a fiber-cut. I am not able to troubleshoot the problem, to date I keep restarting the container when that happens, while trying to figure out if it is related to me or to Azure. Let me know if you resolve, please.
Ivan Bicalho 0 Reputation points

2023-09-25T22:24:19.3433333+00:00

Same here, not sure what's going on, looks like something with Azure, everything was working fine so far.

Answer 1

Anonymous

Same issue. I simply redeployed the container, didn't change anything, only destroyed and re-recreated. We use terraform rather than bicep but yes, same solution but no name changes.

Answer 2

Christian Gitter 0

We had the same issue.
It seems like there has been a change in the container name policy.
If you use Bicep to deploy your ressources you can try to delete the ressources in the portal.
Rename your container name (e.g. "containername-prod") and redeploy it.
We were able to solve the issue this way.

Juha Vuorinen 0 Reputation points

2023-09-26T11:37:08.74+00:00

We also have the same issue ongoing
Ivan Bicalho 0 Reputation points

2023-09-26T11:48:04.8133333+00:00

Not sure if it's the problem, I'm currently using azure cli to create my resources and my container name only have letters and "-". I have two CI's and I use Logic App to start them. Oddly, one of them always fail but the other sometimes work, take a look at the screenshots.

img01.png

img02.png
Luca Maurelli 30 Reputation points

2023-09-26T11:52:07.9033333+00:00

I do not have name policy problem here as well, as far as I can tell. I figured out though that under the Metrics tab of the portal I can see cpu/ram deallocated after the container terminates but there is still some activity in the network metric, as if the container is stuck due to some data networking exchange.
See:
https://learn.microsoft.com/en-us/answers/questions/1375918/azure-container-instance-terminated-but-the-contai
AdrianSilo 0 Reputation points

2023-09-28T06:22:29.1433333+00:00

We have two pipelines utilizing Logic Apps to periodically start container instances. The first encountered this error on Sept 26, which resolved a day later by itself - and now the second is also encountering this as of this morning.
Juha Vuorinen 0 Reputation points

2023-09-28T06:54:29.73+00:00

We have four ACIs and 3 are in transtiong status

Share via

The container group is still transitioning, please retry later.

2 answers

Your answer