azure aci in waiting state

Question

azure aci in waiting state

Chatterjee, Somnath (KM) 26

Azure aci is showing in waiting state.
Eve restart did not work.
Also when trying to deploy again, it is getting timed out after 30 mins every time with the message below :

(None) Subscription deployment didn't reach a successful provisioning state after '00:30:00'.
Code: None
Message: Subscription deployment didn't reach a successful provisioning state after '00:30:00'.

Also the container logs shows nothing.

Have gone through all the topics in this area, did not find any solution yet.

SRIJIT-BOSE-MSFT 4,341 Reputation points Microsoft Employee

2021-12-17T10:55:09.733+00:00

@Chatterjee, Somnath (KM) , we shall need some information about the resource you are trying to deploy to be able to understand the underlying cause and/or mitigation.
Hans Bakker 107 Reputation points

2022-02-17T12:38:40.463+00:00
I have the same issue. This is very annoying, and it gives the feeling that Azure Container Instances is not reliable. I have seen too many reports of people containing issues that were difficult to reproduce.

@SRIJIT-BOSE-MSFT what information do you need?

The issue occurs for me

when ACI is linked to a specific subnet (so using a private IP)

There are no network restrictions (firewall / route table / NSG) on that VNet.

I am using west europe.

I do not get any "resources not available error". It simply hangs in one of these states:

container instances group "Pending" / container "Waiting", no private IP at all

container instances group "Creating" / container "Waiting", 0.0.0.0 assigned as private IP

Nothing in Events - so we're in the dark what is happening under the hood.

Using a different VNet with the same settings seemed to be a workaround, but as the root cause is not fixed, it feels unreliable.
Destin Hebert 45 Reputation points

2024-02-26T16:41:09.0333333+00:00

We are having a similar issue as well. Same error messages that have been reported here with no indication of what the issue is and no logging. We were trying to deploy a real time endpoint for an inference pipeline built in AzureML.

5 answers

Your answer

SRIJIT-BOSE-MSFT 4,341 Reputation points Microsoft Employee

2021-12-17T10:55:09.733+00:00

@Chatterjee, Somnath (KM) , we shall need some information about the resource you are trying to deploy to be able to understand the underlying cause and/or mitigation.
Hans Bakker 107 Reputation points

2022-02-17T12:38:40.463+00:00

I have the same issue. This is very annoying, and it gives the feeling that Azure Container Instances is not reliable. I have seen too many reports of people containing issues that were difficult to reproduce.

@SRIJIT-BOSE-MSFT what information do you need?

The issue occurs for me

when ACI is linked to a specific subnet (so using a private IP)

There are no network restrictions (firewall / route table / NSG) on that VNet.

I am using west europe.

I do not get any "resources not available error". It simply hangs in one of these states:

container instances group "Pending" / container "Waiting", no private IP at all

container instances group "Creating" / container "Waiting", 0.0.0.0 assigned as private IP

Nothing in Events - so we're in the dark what is happening under the hood.

Using a different VNet with the same settings seemed to be a workaround, but as the root cause is not fixed, it feels unreliable.
Destin Hebert 45 Reputation points

2024-02-26T16:41:09.0333333+00:00

We are having a similar issue as well. Same error messages that have been reported here with no indication of what the issue is and no logging. We were trying to deploy a real time endpoint for an inference pipeline built in AzureML.

Answer 1

Chatterjee, Somnath (KM) 26

Also I see that Azure Container instance has private IP as 0.0.0.0
Is that normal ?

Hans Bakker 107 Reputation points

2022-02-17T12:44:02.933+00:00

No, it is not - it should get assigned an IP from the range of the subnet that you linked to it. If you deployed it using a public IP then it should not show "private IP".

Answer 2

Pablo Garza 21

Hi, I'm also stuck on this, any posible solution to this issue?

Answer 3

87808688 6

Same here, I have the same issue when deploying a container instance (Linux) with VNET injection. The private IP address shows 0.0.0.0 instead of my chosen private IP. And the container instance stays in the "creating" state until it stops with the ARM timeout error.

Answer 4

Christian Heinz 0

Same here!

I am also trying to create a Azure Container Instance into a private Subnet, result is the same error as the thread creator described ('Subscription deployment didn't reach a successful provisioning state after '00:30:00'') with no logs and Container State Waiting.

Answer 5

Simon Vitt 0

Same Here! Did anyone find a solution?

Share via

azure aci in waiting state

5 answers

Your answer