Error with Azure CLI 2.46.0 and Bicep if no bicep configuration exists

Question

Error with Azure CLI 2.46.0 and Bicep if no bicep configuration exists

qetza opened this issue a year ago · comments

Guillaume Rouchon commented a year ago

This is autogenerated. Please review and update as needed.

Describe the bug

Command Name
az bicep install

Errors:

Installing Bicep CLI v0.14.85...
The command failed with an unexpected error. Here is the traceback:
No section: 'bicep'
Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 663, in execute
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 726, in _run_jobs_serially
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 697, in _run_job
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 333, in __call__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/custom.py", line 3648, in install_bicep_cli
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/resource/_bicep.py", line 141, in ensure_bicep_installation
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/config.py", line 99, in get
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/config.py", line 94, in get
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/config.py", line 208, in get
  File "configparser.py", line 783, in get
  File "configparser.py", line 1154, in _unify_values
configparser.NoSectionError: No section: 'bicep'

To Reproduce:

Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

install Azure CLI 2.46.0
az bicep install --version {}

Expected Behavior

No error if configuration is not set.

Environment Summary

Windows-10-10.0.17763-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.46.0

Additional Context

This error also happens when running an az deployment command passing a bicep file. It seems that the code is not resilient if no configuration for bicep is specified in the config file.

msftbot · Answer 1 · Wed Mar 08 2023 07:03:09 GMT+0800 (China Standard Time)

Thank you for your feedback. This has been routed to the support team for assistance.

Yong Zhang · Answer 2 · Wed Mar 08 2023 07:03:15 GMT+0800 (China Standard Time)

route to CXP team

Kurt Mueller · Answer 3 · Wed Mar 08 2023 08:54:28 GMT+0800 (China Standard Time)

I can confirm that I receive this same error when running inside an aarch64 devcontainer. I've been installing azure cli via python since apt apparently only supports the x86 architecture.

Here are my specs:

Version: 1.77.0-insider
Commit: bbc87d8ec2453f12c0066e1c30b41cd5bd2aa021
Date: 2023-03-07T05:36:47.728Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin arm64 22.3.0
Sandboxed: Yes

Dawid Holka · Answer 4 · Wed Mar 08 2023 15:23:27 GMT+0800 (China Standard Time)

I have the same problem, the installation works when I set:
az config set bicep.use_binary_from_path=False.
The problem occurs since version 2.46.0.

Pramod Valavala · Answer 5 · Thu Mar 09 2023 05:35:48 GMT+0800 (China Standard Time)

@qetza @kurt-mueller-osumc @dawidholka Thanks for the feedback! We have worked up a PR to address this.

Please do note that despite this error, the bicep CLI is installed and can be used as usual.

Shalvindra K Prasad · Answer 6 · Thu Mar 09 2023 07:13:39 GMT+0800 (China Standard Time)

@qetza @kurt-mueller-osumc @dawidholka Thanks for the feedback! We have worked up a PR to address this.

Please do note that despite this error, the bicep CLI is installed and can be used as usual.

The error breaks automated deployment pipelines though.
I use BitBucket Pipelines for deployment and face this same error message. The pipeline fails at this error message from az deployment ... command in the pipeline.

Dawid Holka · Answer 7 · Thu Mar 09 2023 07:18:06 GMT+0800 (China Standard Time)

@krizskp

@qetza @kurt-mueller-osumc @dawidholka Thanks for the feedback! We have worked up a PR to address this.
Please do note that despite this error, the bicep CLI is installed and can be used as usual.

The error breaks automated deployment pipelines though. I use BitBucket Pipelines for deployment and face this same error message. The pipeline fails at this error message from az deployment ... command in the pipeline.

I also have this problem when running the pipeline and az deployment ... command. I solved this problem by adding at the beginning:

az config set bicep.use_binary_from_path=False
az bicep install

I haven't tested yet how this would work with:
az config set bicep.use_binary_from_path=if_found_in_ci

Michael Elleby · Answer 8 · Fri Mar 10 2023 03:33:42 GMT+0800 (China Standard Time)

@krizskp

@qetza @kurt-mueller-osumc @dawidholka Thanks for the feedback! We have worked up a PR to address this.
Please do note that despite this error, the bicep CLI is installed and can be used as usual.

The error breaks automated deployment pipelines though. I use BitBucket Pipelines for deployment and face this same error message. The pipeline fails at this error message from az deployment ... command in the pipeline.

I also have this problem when running the pipeline and az deployment ... command. I solved this problem by adding at the beginning:
az config set bicep.use_binary_from_path=False
az bicep install
I haven't tested yet how this would work with: az config set bicep.use_binary_from_path=if_found_in_ci

Another workaround is to run the same az command twice, as the first time it will fail and the second time it succeeds.

Karen Tazayan · Answer 9 · Fri Mar 10 2023 17:09:09 GMT+0800 (China Standard Time)

The same error breaks my Azure Pipelines when build agents upgraded to Azure CLI 2.46.0.

inDgenious · Answer 10 · Fri Mar 10 2023 23:37:23 GMT+0800 (China Standard Time)

Breaking Azure Pipeline builds for me too. Tried workaround but still breaking. Currently can't deploy any of my infra from Pipelines. What's the timeframe for the fix?

Steven De Lausnay · Answer 11 · Fri Mar 10 2023 23:57:05 GMT+0800 (China Standard Time)

We have the same issue on our agents. Workaround also don't seem to do the trick for use. Any news on the topic?

BeL8 · Answer 12 · Sat Mar 11 2023 07:55:30 GMT+0800 (China Standard Time)

Same error, resolved by using inline script in additional Task before running the main Task.
inlineScript: |
az config set bicep.use_binary_from_path=False
az bicep install

Ashutosh · Answer 13 · Mon Mar 13 2023 12:18:28 GMT+0800 (China Standard Time)

I am facing same issue bicep install fails. even after setting az config set bicep.use_binary_from_path=False , it produces warning on the console and build fails.

vishnuss10308 · Answer 14 · Mon Mar 13 2023 14:06:41 GMT+0800 (China Standard Time)

I am also facing the same issue in GitLab Pipelines
az deployment group create command is failing with error
ERROR: No section: 'bicep'
Retry worked for az deployment group validate command for the same parameters.

Update: az deployment group create command worked after 4 retries

TenaciousG · Answer 15 · Mon Mar 13 2023 15:27:33 GMT+0800 (China Standard Time)

This is also breaking my Azure Pipelines. Cannot deploy production changes!

Espen H. Kristensen · Answer 16 · Mon Mar 13 2023 16:06:56 GMT+0800 (China Standard Time)

Having same issue with our GitLab pipelines breaking. Any news?

Ricardo Schroeder · Answer 17 · Mon Mar 13 2023 17:53:11 GMT+0800 (China Standard Time)

Any news yet? All our deployments are failing now

Patrick Sengalrayan · Answer 18 · Mon Mar 13 2023 18:49:37 GMT+0800 (China Standard Time)

All deployments failing here as well, on an Agent in a deployment agent pool.

/usr/bin/bash /home/azuredevops/azdoAgent/_work/_temp/azureclitaskscript1678703942369.sh
ERROR: No section: 'bicep'
##[error]Script failed with exit code: 1

Temporary solution:
Until fixed, downgrading version to az cli 2.45 seems to solve the issue. On agent VM run:
sudo apt-get install azure-cli=2.45.0-1~focal

Mind: when fixed, upgrade az cli again!

Karen Tazayan · Answer 19 · Mon Mar 13 2023 19:18:10 GMT+0800 (China Standard Time)

As a temporary solution, I also downgraded all agents to the previous version.

az-core · Answer 20 · Mon Mar 13 2023 19:25:40 GMT+0800 (China Standard Time)

This issue seems related to a recent change
CLI 2.45.0 breaks Github Actions that tried to install a specific version of Bicep
Fix #25510: az bicep: Set bicep.use_binary_from_path to false when installed using Azure CLI

It also breaks pipelines using the latest image mcr.microsoft.com/azure-functions/dotnet:4-dotnet6-core-tools as Azure Cli 2.46.0 is internally referenced and installed.

As mentioned in the thread above, the az deploment command also fails.

For now, last week, we managed to fix this by including command
az config set bicep.use_binary_from_path=false

before az bicep install and az deployment commands. This work around is mentioned above in this thread and also on #25510

Grant Crowe · Answer 21 · Tue Mar 14 2023 08:16:14 GMT+0800 (China Standard Time)

Can also confirm we are getting this error in Gitlad Pipeline deployments using the MS image
image: mcr.microsoft.com/azure-cli

can confirmed az config set bicep.use_binary_from_path=false got me around this also

TenaciousG · Answer 22 · Wed Mar 15 2023 15:26:58 GMT+0800 (China Standard Time)

Is this the same issue that I'm facing when using the AzureResourceManagerTemplateDeployment@3 Azure Pipeline task?
My error message for the past week is:

##[error]Check out the troubleshooting guide to see if your issue is addressed: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting
##[error]Error: Command failed: az bicep build --file /agent/_work/1/s/ARMTemplates/goweb/prod/prod-goweb.bicep
ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: No section: 'bicep'

This is crippling for my ARM deployments! And the workaround by first running this script doesn't do anything for me:

az config set bicep.use_binary_from_path=false
az bicep install

G. Petrakis · Answer 23 · Wed Mar 15 2023 18:05:17 GMT+0800 (China Standard Time)

breaking all pipelines on ubuntu , windows agents appear to be working for now

sandert-k8s · Answer 24 · Wed Mar 15 2023 22:37:04 GMT+0800 (China Standard Time)

Still broken since last week. Workarounds aren't working for us.
If possible, a hotfix would be highly appreciated. Our workload is depending on bicep, which are all failing now.

Dawid Holka · Answer 25 · Thu Mar 16 2023 00:54:03 GMT+0800 (China Standard Time)

Is this the same issue that I'm facing when using the AzureResourceManagerTemplateDeployment@3 Azure Pipeline task? My error message for the past week is:
##[error]Check out the troubleshooting guide to see if your issue is addressed: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops#troubleshooting
##[error]Error: Command failed: az bicep build --file /agent/_work/1/s/ARMTemplates/goweb/prod/prod-goweb.bicep
ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: No section: 'bicep'
This is crippling for my ARM deployments! And the workaround by first running this script doesn't do anything for me:
az config set bicep.use_binary_from_path=false
az bicep install

This workaround works for me with AzureCLI@2 task and setting input: useGlobalConfig: true.

TenaciousG · Answer 26 · Thu Mar 16 2023 17:49:54 GMT+0800 (China Standard Time)

@dawidholka Thanks, didn't get a chance to test it out since my pipelines seem to be working today. Hopefully the issue has been fixed globally.

Daniel Mackay [SSW] · Answer 27 · Thu Mar 16 2023 18:08:47 GMT+0800 (China Standard Time)

I've tried the az config work around, and have now got our bit bucket pipelines working.

Thanks @dawidholka! 😄

John Reilly · Answer 28 · Fri Mar 17 2023 21:44:35 GMT+0800 (China Standard Time)

Seeing this also on GitHub Actions deployments for my Azure Static Web App blog. Failing build: https://github.com/johnnyreilly/blog.johnnyreilly.com/actions/runs/4433656682/jobs/7810249789?pr=459

PR that triggered this: johnnyreilly/blog.johnnyreilly.com#459

PNeergaard · Answer 29 · Fri Mar 17 2023 22:23:52 GMT+0800 (China Standard Time)

We found that this issue may be related to the fact that Bicep is already installed on the agent running the build i.e. if running windows-latest in Azure DevOps. If we remove our "az bicep install" step, deployments run without any issues.

greg · Answer 30 · Sat Mar 18 2023 02:20:37 GMT+0800 (China Standard Time)

Anyone facing this issue when trying to set to false, it causes any Azure Pipelines to fail.

az config set bicep.use_binary_from_path=false
az bicep install

Justin Beeson · Answer 31 · Sat Mar 18 2023 02:31:26 GMT+0800 (China Standard Time)

Anyone facing this issue when trying to set to false, it causes any Azure Pipelines to fail.
az config set bicep.use_binary_from_path=false

az bicep install

I'm not seeing that issue but I put those two lines in their own PowerShell task and set standarderror to false and continueonerror to true because as long as they run (even failing) the next bicep command should work.

greg · Answer 32 · Sat Mar 18 2023 04:00:23 GMT+0800 (China Standard Time)

Thanks adding those two lines in their own PowerShell task worked.

Example

- task: PowerShell@2
  displayName: "Install Bicep"
  inputs:
    targetType: 'inline'
    script: |         
          az config set bicep.use_binary_from_path=false
          az bicep install
    failOnStderr: false
    showWarnings: true
    pwsh: true

Mehrdad Soltani · Answer 33 · Tue Mar 21 2023 07:28:32 GMT+0800 (China Standard Time)

This is an extra burden for us when writing CI/CD pipelines, which is now broken due to this functionality. I have to add the flag use_binary_from_path=False and install Bicep CLI manually, which is really nasty.