Hey everyone! I'm currently deploying a container app environment using Bicep, and it's been running for about 1.5 hours with no signs of progress in the Activity log. I'm wondering if anyone has suggestions on what might be wrong. I noticed that some resource groups were created and then deleted, like 'MC_jollyfield-***-rg_jollyfield-***_australiaeast.' I think these are related to the Kubernetes cluster for the app container environment. Also, I suspect there might be an issue with my managed certificate setup, so I'm thinking of canceling the deployment for now and adding the cert later, especially since I remember a bug related to this from last year. Additionally, I found a solution where I added a workload profile as consumption and specified the resource group name for the infrastructure. I also created delegation subnets in the VNET for the container app environments to avoid issues. Would love to hear your thoughts!
4 Answers
Are you also provisioning Private Links with the same deployment? I had a similar long deployment in the past because the private links weren't approved on the target PaaS resource. Also, if you're configuring a Container App for that environment, it could be the image from your Azure Container Registry (ACR). Sometimes, if the image isn't healthy or not on ACR yet, it can keep the deployment hanging.
I gave up on container apps and functions because of problems like this. Switched to deploying on a VM instead – life became much simpler, but I know that might not be an option for you.
If it’s taking over 10 minutes with no logs, it’s likely a permissions issue. Have you checked those?
Deployments for Azure solutions ending in 'Environment' often take a long time, sometimes the full cycle. It’s not uncommon!
I found out the root cause of my issue and I'll share it shortly.
I've realized it's something in my Bicep code causing this. I’ve updated my original post to include more details.