Comment 7 for bug 1708676

This issue still affects Juju today.

If an error occurs during bootstrap, we DON'T notify the user - instead the Juju client just hangs and the user is left wondering what's happening. They have to ssh into the machine, find the right log file, trawl through the logs...

This is terrible UX, and we should be making a best-effort here to surface any issues that come up during the bootstrap process.