Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container App Revisions become unmanageable after updates (via API or portal) #19285

Open
jackofallops opened this issue May 31, 2022 · 6 comments
Labels
App Services Service Attention Workflow: This issue is responsible by Azure service team.

Comments

@jackofallops
Copy link
Contributor

Container Apps Reports Timeout on LRO despite apparently actually deploying and starting the containers in the revision.

Pasted Graphic 1

API Call returns:

Message="Failed to provision revision for container app 'acctest-capp-220531111719259950'. Error details: Operation expired."

The revision being “created” is the rev4 noted displayed as Provisioned, and the container is started successfully as shown in the App Insights log entry:

“[REDACTED]“,RestAPI,,,"5/31/2022, 10:27:29.835 AM",,,"5/31/2022, 10:26:45.775 AM","1653992805.77502"," * Running on all addresses (0.0.0.0)",stderr,F,"docker.io/jackofallops/azure-containerapps-python-acctest:v0.0.1","acctest-capp-220531111719259950--rev4-6779d76698-6xlmx",5aa611e0a9b2d86717621376de2336d6a21e43fbe6e677189c2828ea4098869b,"11f5c016-0ac7-4a67-b21a-488523b502c0","acctest-cont-220531111719259950","acctest-capp-220531111719259950",,"agreeableground-ab0a055d","ContainerAppConsoleLogs_CL",

However, the service reports "provisioningState”: “Failed”.

The Update configuration (specifically a configuration containing the minimum required properties plus a revisionSuffix), when sent as a Create operation, works correctly. Additionally, if it is the first update to a newly created resource, it also works correctly. If applied as a subsequent update, it fails and the service cannot be updated further, even via the Portal, e.g.

Deploy revision

API Version: 2022-03-01

@tommytroen
Copy link

I am experiencing the same issues ☝️ when deploying updates to a containerapp using bicep and github actions.

@evenh
Copy link

evenh commented Sep 14, 2022

Is this on Microsoft's roadmap yet? As it is a new service with a lot of potential users migrating from Container Instances I think this deserves to be prioritised.

@diegolagospagopa
Copy link

Hi People, please there are any update?

We want to use this feature but without the terraform module, we cannot start to use it.

@bradbeecham
Copy link

Same here. Is this isolated to certain users or how are others using it in production in this state?

@jackofallops
Copy link
Contributor Author

Hi all - Whilst this issue is still outstanding, we've worked together with the service team to establish a workaround to prevent this issue until such time as a long term solution can be found/implemented, so the initial support for this is now in final review stage for the provider in hashicorp/terraform-provider-azurerm#18008

@Ricky-G
Copy link

Ricky-G commented Feb 2, 2023

There are multiple themes going on here. Just so there is no confusion

  1. Terraform support - there is support for this and its tracked here New Service: Containerapps hashicorp/terraform-provider-azurerm#18008
  2. Timeout when deleting a secret, this is what the core of this issue is about, is being tracked here Deleting a secret that is referenced by some revision results in a long running update operation timing out microsoft/azure-container-apps#395

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App Services Service Attention Workflow: This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

7 participants