run-command invoke doesn't produce correct error/status fields

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug az vm run-command invoke reports success even though command execution failed

To Reproduce Execute az vm run-command invoke --ids SOMEID --command-id RunShellScript --scripts “exit 123” or any other command that would fail

Expected behavior Status should be failed (or error)

Environment summary

$ az --version
azure-cli (2.0.38)

Additional context Whatever command I try to run on a Linux VM the error output field is always null and status field successed The logs on the VM report that the program was terminated with the expected error exit status. The message field from az cli output correctly reports the error but I’d expect the that either success or error fields would report the same.

Here’s an example output from a command that doesn’t exist on the system:

{
  "endTime": "2020-07-20T14:45:16.478019+00:00",
  "error": null,
  "name": "807c0bd6-8810-46ff-97f0-d56d6af52fa6",
  "output": [
    {
      "code": "ProvisioningState/succeeded",
      "displayStatus": "Provisioning succeeded",
      "level": "Info",
      "message": "Enable succeeded: \n[stdout]\n\n[stderr]\n/var/lib/waagent/run-command/download/86/script.sh: line 1: asdasd: command not found\n"
    }
  ],
  "startTime": "2020-07-20T14:44:42.274790+00:00",
  "status": "Succeeded"
}

[axayjo]

Closing this issue and tracking this as a feature request on feedback.azure.com. If you’d like to request this feature, please go to this link and upvote it: https://feedback.azure.com/forums/34192--general-feedback/suggestions/42627826-ensure-run-command-invoke-produces-correct-error-s

[gregsmi]

dead link: https://feedback.azure.com/forums/34192--general-feedback/suggestions/42627826-ensure-run-command-invoke-produces-correct-error-s