Azure CLI failing to finish/return from `az vm start ...` command

This is autogenerated. Please review and update as needed.

Describe the bug

I have an Azure DevOps Release Pipeline with the Azure CLI task wherein I have this command run: az vm start --resource-group GROUP --name NAME Last week (the second week of August) the command had been running fine. As of around August 17th, the command began being stuck in the in progress state for up to >90 minutes before I manually canceled it. I repeated it several times, and noticed that the VM was indeed being started, just that the command never finished. I am able to reproduce this locally on my laptop with Azure CLI 2.10.1 as well. I have also tried this command on the Azure Portal cloud shell, where it works fine and finishes quickly. The similar az vm stop works fine on all locations, too.

Command Name az vm start

Errors: Command never finishes, seems stuck as in progress, although the VM is started.

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 start --resource-group {} --name {} --debug

Expected Behavior

The command completes after VM is started, allowing either the Azure CLI release pipeline task to continue or the CLI command prompt to return to user.

Environment Summary

Windows-10-10.0.14393-SP0
Python 3.6.8
Installer: MSI

azure-cli 2.10.1

Additional Context

azurecli1.txt Including output of --debug command after letting it run for several minutes. azurecliPipeline.txt Including output of release pipeline task with debug setting. Release pipeline is on Azure DevOps online, a la https://dev.azure.com/COMPANY

[hobothulhu]

The issue no longer appears present after removing the SqlIaasExtension. I will create a new issue and reference this one if I re-encounter this issue. I appreciate your help, @avirishuv . I wish you a pleasant weekend!

[feacluster]

@feacluster, could you open a new issue with the details that you are seeing? It looks like the original problem described in this issue was with the SqlIaasExtension. If you are using that extension, then please see if the issue goes away if you remove that extension. If your issue is separate from the previous one, then please open a new issue for the CLI team to investigate.

Sure, will do. I’ve opened a ticket through the support portal. So if still unresolved then will open a new issue here. I am not using SqlIaasExtension as far as I know…