Juju 2.8.10 Release Notes

The Juju team is proud to release Juju 2.8.10!

This is a bug-fix release for the 2.8 series.

This release includes important fixes

  • LP #1918695 - Migration of large models does not complete due to timeout
  • LP #1910989 - Juju injecting unwanted metadata in Resources deployed by K8s Charm
  • LP #1918742 - Error in bundle causes juju to panic
  • LP #1918204 - Need a consistent means to know the hostname of a machine
  • LP #1916746 - juju show-status-log shows only one entry while multiple hooks have been executed
  • LP #1915057 - cannot fetch instance information warning message not helpful
  • LP #1914098 - juju bootstrap on aws failed while setting up groups

Additional bugs fixed can be found in the milestone page.

Other improvements

Kubernetes Model Admission

With this release Juju will no longer try to intercept and modify Kubernetes objects of AccessReview to the Juju model. This fixes a serious bug where some workloads where not able to start due to these checks failing.

How do I upgrade?

There are three binaries that make up a Juju deployment - the client, the server and the agents. To upgrade a running system:

Upgrade the client

Make sure you have the version of the Juju CLI that you want running across the system (controller and agents in any deployed models). If you installed the Juju snap, it will automatically be updated daily from the channel you selected, but you might want to sudo snap switch juju --channel=2.8/stable for example, to get a particular version. To get the latest binary from your channel:

snap refresh juju 

Upgrading the Juju client through other channels

Check version

Make sure that you’re using the Juju version you want.

juju version

What to do if Juju reports an old version

Backing up

The controller state can be saved to allow for recovery in case the upgrade process encounters a serious error.

juju create-backup

Upgrade a Juju server

You can see which servers your client knows about, and their versions, with this command:

juju controllers
Controller  ...  Version
azure*      ...  2.8.3  
jaas        ...  2.7.6  

You can instruct a server to upgrade itself to the latest version:

juju upgrade-controller <controller>

How to upgrade the controller

Upgrade deployed agents

Each running model includes a set of Juju agents which manage the communication between your charms and the Juju server. Your model agents remain at the same version until you ask to upgrade them.

juju upgrade-model <model>

How to upgrade your model(s)

Further instructions

For detailed information about the upgrade process please see:

Feedback Appreciated!

Let us know how you’re using Juju! Please ask questions on discourse.charmhub.io, tweet us @juju_devops with the hashtag #juju_devops, and chat with us at #juju on Freenode.

1 Like