azure-cli: az vm image list can't find publisher
Describe the bug
Command Name
az vm image list
Errors:
Publisher: Symantec.test.ru4mp1.latest was not found.
To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.
- Put any pre-requisite steps here…
az vm image list --offer {} --all --location {} --output {} --debug(may only reproduce with the exact ‘az vm image list --offer UbuntuServer --all --location eastus2’ command
Expected Behavior
Environment Summary
Windows-10-10.0.18362-SP0
Python 3.6.6
Shell: powershell.exe
azure-cli 2.0.74
Extensions:
azure-devops 0.11.0
dev-spaces 1.0.3
webapp 0.2.19
Additional Context
Original customer thread https://github.com/MicrosoftDocs/azure-docs-cli/issues/1732 I was able to reproduce it and I’ve sent an email with the debug log to the DL.
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 23 (14 by maintainers)
The publisher data inconsistency has been confirmed to be fixed now. We will investigate the root case and make the changes needed to prevent a persistent data inconsistency in the service.
WRT the current implementation, it is quite possible for the List All Publishers REST API to return a publisher for which the List Offers or List Extension Types API will return an error that the publisher is not found. Under normal conditions this state is transient and should correct itself within a minute and not be permanent as what happened here. It would be safe to assume that the named publisher does not have any available images or extensions in response to the PublisherNotFound error. So, the CLI code changes are also good changes to keep for this item to prevent transient failures.
Hey, I’m from the service team that’s returning the inconsistent publisher data. We have identified 16 instances of the publisher data inconsistency across 17 regions. We are in the process of patching the data today to remove the inconsistency. Not all publishers are impacted in all regions, the range is 1-5 problem publishers per region.
Impacted Publishers: MICROSOFT.AZURE.EXTENSIONS.TEST94A55E3B-0448-4638-867C-6D01304F4BDF-20190219154622 SYMANTEC.TEST.RU2FINAL MICROSOFT.WINDOWSAZURE.COMPUTE.TEST MICROSOFT.TESTSQLSERVER.EDP MICROSOFT.AZURE.EXTENSIONS.TESTB2E612E0-1C8C-40ED-93FE-A169ED7619CB-20190219154622 MICROSOFT.AZURE.NETWORKWATCHER.EDP SYMANTEC.TEST.RU4MP1.LATEST MICROSOFT.SYSTEMCENTER.TEST TRENDMICRO.DEEPSECURITY.TEST MICROSOFT.AZURE.EXTENSIONS.TESTFE504E88-854F-46C7-9775-16CAC9BFCF28-20190219154622 SYMANTEC.TEST.RU4MP1 SYMANTEC.CLOUDWORKLOADPROTECTION.TEST MICROSOFT.COMPUTE.TESTSAR MICROSOFT.SYSTEMCENTER KASPERSKYLAB.SECURITYAGENT MICROSOFT.OSTCEXTENSIONS.EDP
Impacted Regions: WestEurope EastUS eastasia JapanWest EastUS2EUAP KoreaCentral FranceCentral CanadaCentral JapanEast NorthEurope southeastasia BrazilSouth CanadaEast AustraliaEast EastUS2 AustraliaCentral2 CentralUSEUAP
I have reproduced the bug. Using ‘–debug’, you can see this command can get lots of images, but in the end of the output, there is an error when retrieving image info from publisher Symantec.test.ru4mp1.latest. I think I may need to add some fault tolerance mechanism.