[BUG]: AzureContainerAppsV1 fails with: Error: Unable to set the Azure CLI to dynamically install missing extensions. #20781
Comments
github-actions
bot
added
Area: Release
triage
Area: ABTT
|
Any way to downgrade to avoid this CI-killer?? |
|
+1 Same issues started since yesterday |
|
+1 save issue here. just started for us as well. |
|
+1 also here :( |
|
+1 same issue |
|
+1 here as well |
|
+1 Issue reproducing on Microsoft Hosted Environment as well. |
|
+1 breaking the deployment pipeline |
|
This is also occurring in Github actions when using |
|
+1 breaking the pipeline |
|
After updating the action version to v2 in GitHub Action workflow, the job is now running.
@jacknewberry , you can try with v2 |
|
+1 breaking the pipeline |
It's not clear where you're configuring this. I tried
but this gives
I tried
but this gives
(ah i see. haven't had enough coffee :) ) https://github.com/Azure/container-apps-deploy-action 'uses' not 'task' key however I get this error with that
I now realize you provided a snippet for a github workflow, not for a azure pipeline. Might be worth specifying this in your comment. |
|
If it helps, this has started happening with the |
|
This is a CI-killer. Our entire team is blocked. This must be affecting thousands of businesses. Please MS roll back to previous build!! |
|
Also having issues |
|
It looks like there were some changes around azure-cli configuration in the latest image: actions/runner-images@releases/ubuntu24/20250105...releases/ubuntu24/20250113#diff-701349f89aba93398253ed2ff24c17bb6fc3f5790872dea878f711f1aad661cc It now sets WORKAROUNDManually setting the For example: - task: AzureContainerApps@1
displayName: "Deploy image"
env:
AZURE_CONFIG_DIR: $HOME/.azure
inputs:
... |
|
Can confirm, workaround posted above solves the issue |
|
Hi Everyone, Sorry for the inconvenience caused by the recent Ubuntu images updates. Currently we are rolling back Ubuntu images to the previous version - |
|
Having the same issue with a classic azure pipeline (not YAML) and Azure CLI v2 task. I tried the workaround but somehow it did not apply the env variable when set at the task level. I set AZURE_CONFIG_DIR = $Home/.azure at the pipeline level (just regular pipeline variables) and it did the trick. |
|
Hi Everyone, |
Just ran my pipeline that has an AzureContainerApps@1 task and AzureCLI@2 tasks to deploy a Container App Env and a Container App Job. Ran successfully (I confirm it's using the 20250105.1 image) but i still have @nimro 's workaround in place. I'll try to remove the AZURE_CONFIG_DIR pipeline variable and report back. |
|
@DergachevE I confirm that all of my three azure pipeline tasks (Container App Env deploy, Container App deploy, Container App Job deploy) run successfully on the rolled-back agent after removing @nimro 's AZURE_CONFIG_DIR workaround. |
|
Thanks for confirmation. Closing this issue for now |
New issue checklist
Task name
AzureContainerAppsV1
Task version
1.247.1
Issue Description
AzureContainerAppsV1 task started to fail with the following error message:
ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: [Errno 1] Operation not permitted: '/opt/az-config/config'
Traceback (most recent call last):
File "/opt/az/lib/python3.12/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/opt/az/lib/python3.12/site-packages/azure/cli/core/commands/init.py", line 666, in execute
raise ex
File "/opt/az/lib/python3.12/site-packages/azure/cli/core/commands/init.py", line 733, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
##[error]Error Code: [1]
##[error]Error: Unable to set the Azure CLI to dynamically install missing extensions.
Environment type (Please select at least one enviroment where you face this issue)
Azure DevOps Server type
dev.azure.com (formerly visualstudio.com)
Azure DevOps Server Version (if applicable)
No response
Operation system
Ubuntu 22.04
Relevant log output
Full task logs with system.debug enabled
Repro steps
The text was updated successfully, but these errors were encountered: