juju-core 1.16.5
Bug fixes, notably dealing with ensure juju knows machines are terminated.
Milestone information
- Project:
- juju-core
- Series:
- 1.16
- Version:
- 1.16.5
- Released:
- Registrant:
- Curtis Hovey
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- 1 Curtis Hovey, 4 John A Meinel, 3 William Reade
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- 8 Fix Released
Download files for this release
Release notes
juju-core 1.16.5
A new stable release of Juju, juju-core 1.16.5, is now available.
This release replaces 1.16.4.
Getting Juju
juju-core 1.16.5 is available in trusty and backported to earlier
series in the following PPA
https:/
Resolved issues
* service with no units stuck in lifecycle dying
Lp 1233457
* destroy-machine --force
Lp 089291
* destroy-machine --force plays badly with provisioner-
Lp 1259473
* API incompatibility: ERROR no such request "DestroyMachines" on Client
Lp 1252469
* juju destroy-machine is incompatible in trunk vs 1.16
Lp 1253643
* juju get give a "panic: index out of range" error
Lp 1227952
* [maas] juju set-env fails after upgrading to 1.16.2+
Lp 1256179
* juju destroy-environment destroys other environments
Lp 1257481
Notable Changes
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”.
Finally
We encourage everyone to subscribe the mailing list at
juju-dev@
Changelog
This release does not have a changelog.
0 blueprints and 8 bugs targeted
| Bug report | Importance | Assignee | Status | |||
|---|---|---|---|---|---|---|
| 1089291 | #1089291 | destroy-machine --force | 2 Critical | William Reade | 10 Fix Released | |
| 1233457 | #1233457 | service with no units stuck in lifecycle dying | 2 Critical | William Reade | 10 Fix Released | |
| 1253643 | #1253643 | juju destroy-machine is incompatible in trunk vs 1.16 | 2 Critical | John A Meinel | 10 Fix Released | |
| 1256179 | #1256179 | [maas] juju set-env fails after upgrading to 1.16.2+ | 2 Critical | John A Meinel | 10 Fix Released | |
| 1227952 | #1227952 | juju get give a "panic: index out of range" error | 3 High | Curtis Hovey | 10 Fix Released | |
| 1252469 | #1252469 | API incompatability: ERROR no such request "DestroyMachines" on Client | 3 High | John A Meinel | 10 Fix Released | |
| 1257481 | #1257481 | juju destroy-environment destroys other environments | 3 High | John A Meinel | 10 Fix Released | |
| 1259473 | #1259473 | destroy-machine --force plays badly with provisioner-safe-mode | 3 High | William Reade | 10 Fix Released | |
