Was not able to deploy container into ACA

Villamor Navarro 0 Reputation points
2023-05-26T10:27:59.42+00:00

Hi,

Bicep deployment of container worked in previous day however the same scripts was use to update the existing deployment did not work.

Steps that happened:

  • Deploy ACA into ACA environment that took too long then cancel.
  • Deleted manually the container from the ACA environment
  • Deploy again fresh, but deployment just keep on spinning and giving status of InternalServerError in the resource deployments in the portal
  • Finally cli says timeout

Operations details:

{
    "status": "Failed",
    "error": {
        "code": "InternalServerError",
        "message": "Internal server error occurred. correlation ID: aace9288-077b-4d4e-b0a9-bf452ff5cdf9"
    }
}
Azure Container Apps
Azure Container Apps
An Azure service that provides a general-purpose, serverless container platform.
325 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. navba-MSFT 19,655 Reputation points Microsoft Employee
    2023-05-30T05:40:28.52+00:00

    @Villamor Navarro Thanks for reaching out to Microsoft Q&A forum. Apologies for the delay in response. I see that you are facing an issue with the Azure Container App deployment.

    1. Did you try the deployment in a different region (location) and check if that helps ?
    2. If you are using AzureCLI, Could you please ensure that you have used the most recent version of containerapp extension ? Here is the command to update to the most recent containerapp extension:
      `az extension update -n containerapp`
    3. Also update your Azure CLI to the most recent version and test again.
    4. If this a transient deployment failure, Could you please retry the same and check if the deployment succeeds now ?

    If you are still encountering the same issue, please share the below details over email to AzCommunity[At]Microsoft[Dot]Com with Subject : Attn NAVBA, so that I can look at the backend logs to identify the cause of the issue:

    1. Is the issue occurring when trying to create a new Container App Environment, or is the issue occurring when trying to create/update a Container App?

    Note: Container Apps are deployed to a Container App Environment.

    Container App Environment resource id: /subscriptions/<subscriptionId>/resourceGroups/<resourcegroup>/providers/Microsoft.App/kubeEnvironments/<containerapp-environment>

    1. Default domain (Myname-randomid1.region.azurecontainerapps.io ).

    Note: If Container App Environment provisioning fails, the resource will be created in a failed state. Thus it is appropriate to get the Container App Environment resource id and Default domain even if deployment fails.

    Container App resource id (if deploying a Container App): /subscriptions/<subscriptionId>/resourceGroups/<resourcegroup>/providers/Microsoft.App/containerApps/<containerapp-name>

    1. UTC Date/time of the deployment operation?
    2. Correlation Id
    3. Details about the issue, specific error message, and error code?
    4. Is the Container App Environment associated with a VNET? If yes, what is the subnet resource id? A subnet resource id is in the format /subscriptions/subscriptionid/resourceGroups/resourcegroup/providers/Microsoft.Network/virtualNetworks/vnetname/subnets/subnetname
    0 comments