bug when 'vm list ' in mode arm
CLI Version: 0.10.9 OS Type: Mac Installation via: npm / brew / win-or-mac installer / docker / github repo
Mode:ARM
Environment: Azure China Cloud
Description:
azure vm show command doesn't output VM name.
when "azure vm image list xxx"
- Getting virtual machine image skus (Publisher:"coreos" Offer:"coreos" Location:"chinaeast") error: The resource type 'locations/publishers' could not be found in the namespace 'Microsoft.Compute' for api version '2016-04-30-preview'. The supported api-versions are '2015-05-01-preview,2015-06-15,2016-03-30'. error: Error information has been recorded to /Users/sunvooker/.azure/azure.err error: vm image list command failed
Hi,
I have same issue and I tested some scenarions:
- Azure Cli: 0.10.08 - Node: 7.4.0 - OS: RHEL 7.3 - Result: OK
- Azure Cli: 0.10.09 - Node: 7.4.0 - OS: CentOS - Result: Error
- Azure Cli: 0.10.09 - Node: 7.4.0 - OS: RHEL 7.3 - Result: Error
- Azure Cli: 0.10.09 - Node: 4.7.0 - OS: Windows Server 2016 - Result: Error
- Azure Cli: 0.10.08 - Node: 4.7.0 - OS: Windows Server 2016 - Result: OK
I look forward the fix for that.
You can find here the steps for downgrade:
npm uninstall -g azure-cli
npm cache clear -g
wget -N https://github.com/Azure/azure-xplat-cli/releases/download/v0.10.8-December2016/azure-cli.0.10.8.tar.gz
npm install -g azure-cli.0.10.8.tar.gz
Thank you for your help.
add 1
@huangpf - Please take a look at this issue.
Service needs to be upgrade there, or the new client with new API version can't be used there. @amarzavery which way do you think is more practical?
Either the service should upgrade or the compute team should recommend what is the version of Azure-CLI that can be used based on the latest api-version deployed in AzureChina. Do you think 0.10.7 of azure-cli will work?
Service upgrade is on the way, but there is no official timeline.
I don't keep all the client-service API version mapping records.
But there should be an ARM command to list what API versions are supported by each region. If it doesn't match the version CRP commands are using, then it means users have to downgrade the client to its previous version.
By this way, the API version matching can be shown to users, and it's by design that there will be mismatches.