You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
az feedback auto-generates most of the information requested below, as of CLI version 2.26.0
Describe the bug
After Updating the azure-cli on the Mac (Version 11.4) with brew upgrade I got the following error messages.
❯ az vm list
/usr/local/Cellar/azure-cli/2.26.0/libexec/bin/python: No module named azure.cli.__main__; 'azure.cli' is a package and cannot be directly executed
or while finding module specification for 'azure.cli' (ModuleNotFoundError: No module named 'azure')
So I was playing with different Python Versions etc. But nothing helped.
So I was going to install the python modules myself:
pip install azure.cli
pip install azure
Error output
[...]
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts.
azure 4.0.0 requires azure-batch~=4.1, but you have azure-batch 10.0.0 which is incompatible.
azure 4.0.0 requires azure-graphrbac~=0.40.0, but you have azure-graphrbac 0.60.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-advisor~=1.0, but you have azure-mgmt-advisor 9.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-applicationinsights~=0.1.1, but you have azure-mgmt-applicationinsights 1.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-authorization~=0.50.0, but you have azure-mgmt-authorization 0.61.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-batch~=5.0, but you have azure-mgmt-batch 15.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-billing~=0.2.0, but you have azure-mgmt-billing 6.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-cdn~=3.0, but you have azure-mgmt-cdn 11.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-cognitiveservices~=3.0, but you have azure-mgmt-cognitiveservices 12.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-compute~=4.0, but you have azure-mgmt-compute 21.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-containerregistry~=2.1, but you have azure-mgmt-containerregistry 8.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-containerservice~=4.2, but you have azure-mgmt-containerservice 16.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-cosmosdb~=0.4.1, but you have azure-mgmt-cosmosdb 6.4.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-datalake-analytics~=0.6.0, but you have azure-mgmt-datalake-analytics 0.2.1 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-datamigration~=1.0, but you have azure-mgmt-datamigration 4.1.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-devtestlabs~=2.2, but you have azure-mgmt-devtestlabs 4.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-dns~=2.0, but you have azure-mgmt-dns 8.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-eventgrid~=1.0, but you have azure-mgmt-eventgrid 9.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-eventhub~=2.1, but you have azure-mgmt-eventhub 4.1.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-iotcentral~=0.1.0, but you have azure-mgmt-iotcentral 4.1.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-iothub~=0.5.0, but you have azure-mgmt-iothub 2.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-keyvault~=1.0, but you have azure-mgmt-keyvault 9.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-loganalytics~=0.2.0, but you have azure-mgmt-loganalytics 8.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-marketplaceordering~=0.1.0, but you have azure-mgmt-marketplaceordering 1.1.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-media~=1.0.0rc2, but you have azure-mgmt-media 3.1.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-monitor~=0.5.2, but you have azure-mgmt-monitor 2.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-network~=2.0, but you have azure-mgmt-network 19.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-policyinsights~=0.1.0, but you have azure-mgmt-policyinsights 0.5.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-rdbms~=1.2, but you have azure-mgmt-rdbms 8.1.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-recoveryservices~=0.3.0, but you have azure-mgmt-recoveryservices 1.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-recoveryservicesbackup~=0.3.0, but you have azure-mgmt-recoveryservicesbackup 0.12.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-redis~=5.0, but you have azure-mgmt-redis 7.0.0rc2 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-reservations~=0.2.1, but you have azure-mgmt-reservations 0.6.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-resource~=2.0, but you have azure-mgmt-resource 18.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-search~=2.0, but you have azure-mgmt-search 8.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-servicebus~=0.5.1, but you have azure-mgmt-servicebus 6.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-servicefabric~=0.2.0, but you have azure-mgmt-servicefabric 0.5.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-signalr~=0.1.0, but you have azure-mgmt-signalr 1.0.0b2 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-sql~=0.9.1, but you have azure-mgmt-sql 0.29.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-storage~=2.0, but you have azure-mgmt-storage 18.0.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-trafficmanager~=0.50.0, but you have azure-mgmt-trafficmanager 0.51.0 which is incompatible.
azure-mgmt 4.0.0 requires azure-mgmt-web~=0.35.0, but you have azure-mgmt-web 2.0.0 which is incompatible.
[...]
Expected behavior
brew upgrade should not brake azure-cli
Environment summary
MacOS 11.4
Python: Python 3.9.6
Azure-CLI: 2.26.0
PIP: pip 21.1.3 (python 3.9)
HomeBrew
Additional context
I don't know why the azure-cli broke, however I believe a custom python version was included (but am unsure), however now the python is set as symlink.
> ls -la /usr/local/Cellar/azure-cli/2.26.0/libexec/bin/python
[REDACTED] /usr/local/Cellar/azure-cli/2.26.0/libexec/bin/python -> ../../../../../opt/[email protected]/Frameworks/Python.framework/Versions/3.9/bin/python3.9
The text was updated successfully, but these errors were encountered:
ghost
added
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
labels
Jul 8, 2021
0hlov3
changed the title
HomeBrew az Version 2.26.0
HomeBrew Brew update brakes az-cli Version 2.26.0
Jul 8, 2021
ghost
removed
the
needs-triage
This is a new issue that needs to be triaged to the appropriate team.
label
Jul 8, 2021
yonzhan
added
Packaging
and removed
customer-reported
Issues that are reported by GitHub users external to the Azure organization.
question
The issue doesn't require a change to the product in order to be resolved. Most issues start as that
labels
Jul 8, 2021
Describe the bug
After Updating the azure-cli on the Mac (Version 11.4) with brew upgrade I got the following error messages.
So I was playing with different Python Versions etc. But nothing helped.
So I was going to install the python modules myself:
Error output
But now everything works as expected.
To Reproduce
Expected behavior
brew upgrade should not brake azure-cli
Environment summary
Additional context
I don't know why the azure-cli broke, however I believe a custom python version was included (but am unsure), however now the python is set as symlink.
The text was updated successfully, but these errors were encountered: