juju-core 1.16.5 is released
curtis at canonical.com
Wed Dec 11 15:10:25 UTC 2013
A new stable release of Juju, juju-core 1.16.5, is now available.
This release replaces 1.16.4.
juju-core 1.16.5 is available in trusty and backported to earlier
series in the following PPA
* service with no units stuck in lifecycle dying
* destroy-machine --force
* destroy-machine --force plays badly with provisioner-safe-mode
* API incompatibility: ERROR no such request "DestroyMachines" on Client
* juju destroy-machine is incompatible in trunk vs 1.16
* juju get give a "panic: index out of range" error
* [maas] juju set-env fails after upgrading to 1.16.2+
* juju destroy-environment destroys other environments
Juju may report the status of a service and machine that was terminated
outside of Juju. Juju did not notice that the machine is gone. This
release provides minor fixes to identify the case, and a feature to
explicitly tell juju that the machine is gone.
juju destroy-machine --force
The destroy-machine command will destroy the machine as needed, and
remove it from its list of available machines. Machines that are
responsible for the environment cannot be destroyed. Machines running
units or containers can only be destroyed with the --force flag; doing
so will also destroy all those units and containers without giving them
any opportunity to shut down cleanly.
Future version of Juju will notice when machines _disappear_ without the
need of “destroy-machine --force”.
We encourage everyone to subscribe the mailing list at
juju-dev at lists.canonical.com, or join us on #juju-dev on freenode.
Canonical Cloud Development and Operations
More information about the Juju