Juju 2.7.6 Release Notes

The Juju team is proud to release Juju 2.7.6! This is a bugfix release for the 2.7 series.

This release includes fixes to the following issues:

  • LP #1869275 - [subordinate] main unit did not get subordinate installed
  • LP #1873070 - High load on the primary mongodb controller unit
  • LP #1854635 - ‘install’ hook does not get executed on CAAS models
  • LP #1867886 - change in default lxd profile
  • LP #1869883 - Kubernetes Multicloud controller Passing wrong IP to external Kubernetes
  • LP #1871066 - Migration fails with stack trace
  • LP #1870478 - k8s remote exec overwrites PATH

The full listing can be found in the milestone page. Look for issues classified as “Fix Released”.

How do I install Juju?

The best way to get your hands on this release of Juju is to install it as a snap:

sudo snap install juju --classic

Other packages are available for a variety of platforms, including Windows and macOS. Refer to the full Juju installation documentation.

Those subscribed to a snap channel should be automatically upgraded. If you’re using the PPA or Homebrew for macOS, you should see an upgrade available.

How do I upgrade?

Upgrading Juju is a multi-step process:

  • upgrade the client (the Juju binary that you interact with on the command-line)
  • (recommended) verify that the client upgrade was successful
  • (recommended) back up the controller
  • upgrade the controller
  • upgrade models

Upgrade the client

If you’ve installed Juju via the snap, your Juju will automatically be installed overnight. To force the update, run:

snap refresh juju 
Upgrading the Juju client through other channels

If you’re using the PPA:

sudo apt update
sudo apt upgrade

On Homebrew for macOS:

brew update
brew upgrade

Check version

To prevent any confusion in later steps, ensure that you’re using the new Juju version.

juju version
What to do if Juju reports an old version

Check your $PATH environment variable and that you’ve installed the new version correctly.

On Linux and macOS, use the env command to inspect the environment. On MS Windows, use SET.

Backing up

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

juju create-backup

Upgrading controllers

Juju includes a command that instructs the controller to upgrade itself to the latest version.

juju upgrade-controller
How to upgrade the controller

First, check that you’re interacting with the intended controller. The juju models command reports the current controller on the first line.

juju models

To verify what will occur, use the --dry-run option.

juju upgrade-controller --dry-run

When you’re happy, omit the flag:

juju upgrade-controller

Upgrade models

Your models remain at the same version until you have explicitly told Juju to upgrade them.

juju upgrade-model
How to upgrade your model(s)

Check that you’re operating in the correct model. juju model highlights the current model with an asterisk:

juju models

To verify what will occur, use the --dry-run option.

juju upgrade-juju --dry-run

When you’re happy, omit the flag:

juju upgrade-juju

Further instructions

Juju’s documentation pages provide detailed information about the upgrade process:

Feedback Appreciated!

We encourage everyone to let us know how you’re using Juju. Please ask questions on on Discourse, send us a message to our Twitter account @juju_devops, tweet using the hashtag #juju_devops, and chat with us at #juju on Freenode via IRC or Matrix.

1 Like

Is it possible to join a AWS controller now to jimm @martin-hilton?

JAAS and Juju have different release cycles, so a Juju release does not imply any particular JAAS fixes have landed. Having said that, I asked for an expedited rollout of the JIMM fix for AWS credential missing tag issue and I believe that got landed yesterday. I have not tried it myself to confirm the fix.

1 Like