Comment 6 for bug 1638332

As of 2.2-beta3, I observed the following behavior with a three-machine model and one machine down.

dparrish@maasrr0:/home/dparrish
$ juju run --all -- uname -r
- MachineId: "2"
  Stdout: |
    4.4.0-77-generic
- MachineId: "4"
  Stdout: |
    4.4.0-77-generic

ERROR timed out waiting for result from: machine 3

[ timeout was 5 minutes ]

dparrish@maasrr0:/home/dparrish
$ juju show-action-status --name juju-run
actions:
- id: 37b9c667-f7bb-4498-83bd-fb67dcff2f05
  status: completed
  unit: machine-2
- id: c1e3e42f-4747-495f-8fce-9f93124309f1
  status: pending
  unit: machine-3
- id: 895cf3de-7ea6-47ff-8860-10322dcd6481
  status: completed
  unit: machine-4

[ machine 3 brought back up ]

dparrish@maasrr0:/home/dparrish
$ juju show-action-status --name juju-run
actions:
- id: 37b9c667-f7bb-4498-83bd-fb67dcff2f05
  status: completed
  unit: machine-2
- id: c1e3e42f-4747-495f-8fce-9f93124309f1
  status: completed
  unit: machine-3
- id: 895cf3de-7ea6-47ff-8860-10322dcd6481
  status: completed
  unit: machine-4

[ action for machine-3 now shows completed ]

Where did stdout/stderr get logged if anywhere? On the controller node, machine-0.log shows the action [initiation?] being logged, but didn't find any record of it in default-model machine:/var/log/juju/machine-<n>.log.

Other than this, it appears the behavior has changed for the better. Fully fixed as freyes was seeking?