Skip to content

EES-6044 infrastructure bicep deployments are failing due to bug in azure cli #5794

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

Conversation

benoutram
Copy link
Collaborator

ℹ️ This applies the same changes to the Public API, Analytics, and Data Screener pipelines that were already made to the Search infrastructure pipeline by #5770 ℹ️

This PR adds a temporary workaround to stop Bicep deployments failing due to a bug in Azure CLI 2.71.0.

The error when starting the Bicep deployment is

No such file or directory: '/home/vsts/work/_temp/.azclitask/bin/bicep'

Between 08/04/25 and 09/04/25 version 2.71.0 with the bug appears to have rolled out gradually across all agents and now it's blocking all of our infrastructure deployments. We can see the last successful run of the Bicep deployment on 08/04/25 used Azure CLI 2.70.0.

2.71.0:
image (1)

2.70.0:
image (3)

Other changes

  • Add step to Upgrade Azure CLI and extensions
  • Remove unnecessary 'az bicep install' command
  • Formatting

@benoutram benoutram merged commit 3f899a6 into dev Apr 15, 2025
4 checks passed
@benoutram benoutram deleted the EES-6044-Infrastructure-bicep-deployments-are-failing-due-to-bug-in-Azure-CLI branch April 15, 2025 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants