The Juju team is proud to release Juju 2.5.3!
This is a bug fix release. An additional enhancement is that unit leadership as reflected in status is derived from the raft data model rather than the mongo database. Other noteworthy fixes include:
- LP #1818245 - goal-state relation data endpoint names
- LP #1816170 - KVM instances fail at creation with: ‘Failed to get shared “write” lock Is another process using the image?’
- LP #1501475 - MAAS node names are displayed in status instead of the API URL.
Additional bugs fixed can be found in the milestone page.
How do I get it?
The best way to get your hands on this release of Juju is to install it as a
sudo snap install juju --classic
Other packages are available for a variety of platforms. Please see the online documentation at https://docs.jujucharms.com/reference-install. Those subscribed to a snap channel should be automatically upgraded. If you’re using the ppa or homebrew, you should see an upgrade available.
We encourage everyone to let us know how you’re using Juju. Join us on Discourse at https://discourse.jujucharms.com/, send us a message on Twitter using the hashtag #jujucharms, and join us at #juju on freenode.