azure-cli: `az vm run-command invoke` returns Deployment Failure with message "Finished executing command"

@Drewm3 I don’t think you have adequately addressed this issue. I have encountered the same behavior as the original reporter. This isn’t a matter of getting the script to run, but instead a problem with retrieving error stream information from the script sent to the VM. The issue from what I can tell is that the script on the VM is not returning the stderr / stdout data back to the machine that invoked the az run-command. I don’t think this has anything to do with the user the account runs under. Perhaps the azure agent could be involved here in terms of permissions, but the key point is that the script neither aborts as expected nor pipes back the error when there are issues, despite the output claiming an error occurred.

All you have to do to reproduce this is send an <az vm run-command invoke --command-id RunPowerShellScript --scripts @myscript.ps1> command that has an error in the myscript.ps1 body and attempt to troubleshoot it as you normally would troubleshoot any other script. So far as I can tell, the only way to determine what the error was is to go here on the VM: C:\Packages\Plugins\Microsoft.CPlat.Core.RunCommandWindows\1.1.2\Status

I would recommend trying to push a script with errors and troubleshoot that without logging onto the VM. If you are able to do that in a manner that is straightforward, please pass that information along. Otherwise, as far as I can tell this needs improvement.

Hi,

I’m running the azure-cli (2.0.74) on a MacOs (10.14.6) and I’m getting the same error.

This is how I run:

az vm run-command invoke \
        --command-id RunPowerShellScript \
        --name $VM_NAME \
        -g $RESOURCE_GROUP  \
        --scripts @myscript.ps1 \
        --parameters "arg1=$STORAGE_ACCOUNT_NAME" "arg2=$STORAGE_KEY"

Deployment failed. Correlation ID: 3f4d9971-8e39-4223-b9c0-3e2c146b5748. VM has reported a failure when processing extension ‘RunCommandWindows’. Error message: “Finished executing command”.

I tested my myscript.ps1 directly in the VM and it works fine.

param(
    [string]$storageAccountName,
    [string]$key,
    [string]$fileShareName
)

Invoke-Expression -Command "cmdkey /add:$storageAccountName.file.core.windows.net /user:Azure\$storageAccountName /pass:$key"

New-PSDrive -Persist -Name "Z" -PSProvider "FileSystem" -Root "\\$storageAccountName.file.core.windows.net\$fileShareName" -Scope "Global"

Any ideas?