My Container App starts ok, but then I see an error, ingress routes not ready

Paul Davies 0

Deployed App, to Container App Env. I can see it started ok, according to its logs.
Shortly after it looks like it wants to set traffic to 100% and then I see this in the logs:
Error : ingress routes not ready",ContainerAppFailure
It tries this for about 20 mins and then the replica revision is marked as failed.

Shireesha Eeraboina 1,900 Reputation points Microsoft External Staff

2024-11-25T14:37:44.43+00:00

Hi @Paul Davies ,

Welcome to the Microsoft Q&A Platform! Thank you for reaching out with your question.

It seems you are experiencing an issue with your deployed app in the Container App environment. Specifically, you're seeing an error in the logs stating "ingress routes not ready," which is causing the replica revision to fail after about 20 minutes.

Here are a few steps you can try to resolve the issue:

1.Check the status of the ingress controller: You can check the status of the ingress controller by running the following command in the Azure CLI:

az containerapp domain show-ingress-controller-status --name <container-app-name> --resource-group <resource-group-name>

This command will show you the status of the ingress controller and any errors that may be occurring.

2.Check the status of your app: You can check the status of your app by running the following command in the Azure CLI:

az containerapp show --name <container-app-name> --resource-group <resource-group-name>

This command will show you the status of your app and any errors that may be occurring.

3.Check the logs for your app: You can check the logs for your app by running the following command in the Azure CLI:

az containerapp logs --name <container-app-name> --resource-group <resource-group-name>

This command will display the logs for your app and any potential errors.

4.Check the configuration of your app: Ensure that your app is configured correctly and that all required environment variables are set.

If none of these steps resolve the issue, here is a link to the Azure Container Apps documentation that may be helpful: Azure Container Apps Documentation

I hope this helps! Let me know if you have any further questions.

Thank you.
Shireesha Eeraboina 1,900 Reputation points Microsoft External Staff

2024-11-26T13:54:26.9033333+00:00

Hi @Paul Davies ,

Checking in to see if you had a chance to review my previous response and provide the requested information. We're eager to help you resolve your issue, and having the necessary information will allow us to do so more effectively.

Thankyou.
Paul Davies 0 Reputation points

2024-11-26T15:45:27.07+00:00

Hi @Shireesha Eeraboina
Thanks for the tips. The command "az containerapp domain show-ingress-controller-status" returned "'domain' is misspelled or not recognized by the system"
The other tips only continue to confirm something is wrong.
It is getting worse - sometimes taking up to an hour.
Pattern is the same, new Revision is deployed, I can see it start ok, but then the dreaded "ingress routes not ready" in the system logs, repeated over and over until the new revision is fully activated.
Only slight difference from the commands and the show one is that the provisioningStatus is failed (runningStatus is Running) . This is different from when I run the command az containerapp revision list, where it has the ProvisioningState as Provisioned
Any further suggestions?
Thanks
Paul
Shireesha Eeraboina 1,900 Reputation points Microsoft External Staff

2024-11-27T09:03:25.3333333+00:00

Hi @Paul Davies,

Thank you for the additional information. Based on the error message you received when running the "az containerapp domain show-ingress-controller-status" command, it seems that the command may not be recognized by the system.

Here are a few additional steps you can try to resolve the issue:

1.Check the status of the ingress controller using kubectl:

You can check the status of the ingress controller using kubectl by running the following command:

kubectl get ingress -n <namespace>

This command will show you the status of the ingress controller and any errors that may be occurring.

2.Check the logs for the ingress controller:

You can check the logs for the ingress controller by running the following command:

kubectl logs -n <namespace> <ingress-controller-pod-name>

This command will display the logs for the ingress controller and any potential errors.

3.Check the configuration of your app:

Ensure that your app is configured correctly and that all required environment variables are set.

If none of these steps resolve the issue, it may be helpful to review the https://learn.microsoft.com/en-us/azure/container-apps/ for additional troubleshooting steps.

I hope this helps! Let me know if you have any further questions.

Thank you.
Shireesha Eeraboina 1,900 Reputation points Microsoft External Staff

2024-11-28T12:08:14.6333333+00:00

Hi @Paul Davies ,

Following up to see if the above answer was helpful. if you have any further query do let us know.

Thankyou.
antonio.policastro 0 Reputation points

2025-03-05T08:36:58.15+00:00

Is it even possibile to use kubectl to interact with azure container apps? I can feel the smell of some AI generated nonsense.
Shireesha Eeraboina 1,900 Reputation points Microsoft External Staff

2025-03-06T06:42:51.3733333+00:00

Hi @antonio.policastro ,

It is not possible to use kubectl with Azure Container Apps because it is a managed service that hides the underlying Kubernetes infrastructure.

Share via

My Container App starts ok, but then I see an error, ingress routes not ready

Your answer