Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Summary
This article explains how to fix an operational failure that happens when a container group remains in a transitioning state indefinitely in Azure Container Instances (ACI). The article also explains failures that happen during container group operations to start, restart, stop, or delete a container group.
Symptoms
When you send a start or stop operation to a container group, you get the following error message.
InternalErrorCode - "ContainerGroupTransitioning"
StatusCode - "409"
Message - "The container group '<container-group-name>' is still transitioning, please retry later."
Cause
Cause 1: After stop operation
During a continuous stop operation of the container group, system sidecar containers in the container group don't stop in time. This delay causes the container group to stay in a transitioning state.
Cause 2: After start operation
The stopped state for the previous operation didn't reach the system yet or didn't reach it correctly (known platform issue). This problem causes the container group to stay in a transitioning state.
Solution 1
Try the following steps to resolve the issue:
- Wait until the container group is fully stopped to allow the system sidecars to fully terminate. Wait at least 10 seconds between operations.
- If the container is deployed by using an Azure Logic App, check the state of the container and then ensure the status is Stopped before you issue a start operation.
- For job container groups (process runs once and exits, restart policy is
Never) in a Terminated state, issue a stop operation before a start operation to ensure the correct status is propagated. You can also issue a restart operation. A restart operation avoids a new container group deployment and instead restarts the application process inside the container.
Note
As a best practice, always issue a stop operation before a start operation to ensure the correct status is propagated. If you start a container group that already has a running container, you might cause the transitioning state problem.
Solution 2: Open a support ticket
If the previous solutions don't fix the problem and you still encounter the error message, open a support ticket.