juju presents no commands to reboot a unit

[Nick Moffitt]

While dealing with a production system in EC2, I found myself with an unresponsive unit. I did not have any ec2 tools to hand (having deployed and managed everything via juju) so it was some work to bounce this system and get it responding again.

Presumably every cloud substrate juju runs on has the notions of a soft reboot as well as a hard stop and start for an instance. Could it please be exposed via the juju CLI?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: juju 2.0~beta12-0ubuntu1.16.04.1
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Aug 8 11:09:07 2016
InstallationDate: Installed on 2014-05-29 (801 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PackageArchitecture: all
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Canonical Juju QA Bot (juju-qa-bot)]

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.