The Juju team is proud to release Juju 2.5.1!
This is a release primarily to address various performance issues found when running at scale. The major issues encountered related to start up of controllers and abnormal behaviour of leadership, both when the controllers are under heavy load.
There’s also a couple of cross model relations fixes, including a fix for allowing multiple offers of a single application.
Important information for older clients
This version reverts a change to larger socket buffer sizes to reduce memory overhead caused by many connections to the controller API. This will cause clients older than Juju 2.2 to have an error that looks like
ERROR codec.ReadHeader error: error receiving message: unexpected end of JSON input
If you hit this please update your Juju client to one that is Juju 2.2 or later.
- LP #1815179 - It is not possible to actively use two offers of the same application at the same time
- LP #1813151 - cmr: remote SAAS status incorrectly reported in consuming model
- LP #1807735 - Juju controller cannot connect to itself
- LP #1810331 - Mid-hook lost leadership issues
- LP #1813104 - Massive goroutine leak (logsink 2.5.0)
- LP #1813261 - api-server and http-server get stuck in “state: stopping”
- LP #1813867 - Hubwatcher caches last modified revno for all docs (memory consumption)
- LP #1814556 - lease Manager should not evaluate all Leases and all Blocks on every loop()
- LP #1811700 - GetMeterStatus called too frequently
- LP #1815719 - repeated ErrInvalid can cause lease.Manager to be stopped
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.