The Juju team is proud to release Juju 2.8.2!
The Juju team is proud to release Juju 2.8.2! This is a bugfix release for the 2.8 series.
Juju has a new interactive shell. It is available for testing in the 2.8 edge snap and upcoming 2.8.2 release candidate. To invoke the shell, simply run juju without any arguments. The prompt will tell you your current controller and model and who you are logged in as. You can run any Juju command, including those which require prompts, and coloured output also works as expected. There’s also support for command history search via Ctrl+R, Ctrl+S, line editing navigation via Ctrl+A and Ctrl+E e…
This release includes fixes to the following issues:
- LP #1849746 - dump-model fails if a machine is allocating
- LP #1886369 - dump-model fails if one or more units are in error / executing state
- LP #1877380 - juju storage should use UUIDs in fstab, and possibly set mount option “nofail”
- LP #1879972 - juju model-config does not export in a way that is reusable
- LP #1880422 - Bootstrapping manual controller on arm64 fails
- LP #1869939 - Unable to add credential for Azure cloud
- LP #1887887 - azure instance type selection is broken
- LP #1884490 - Cannot bootstrap with vSphere data center under a folder
- LP #1890828 - relation data lost during upgrade to juju 2.8.1
- LP #1891524 - Deploying a bundle with caas charm specific setting fails on subsequent deploy
- LP #1892216 - Can’t set application version string in K8s charm
The entire list can be found on the milestone’s page .
Upgrading from 2.8.0 on k8s
If you are running a k8s deployment on 2.8.0, there are extra steps needed to upgrade that deployment to this release.
How to upgrade Juju from 2.8.0 when using Kubernetes If you are using Juju 2.8.0 with Kubernetes and want to upgrade the following steps need to be performed manually. These steps only need to be performed if you have a Juju Kubernetes Controller or are running Kubernetes models. If your current version is not 2.8.0 then these this document can be safely ignored. Upgrading A Juju Kubernetes Controller From 2.8.0 The following is a list of steps that need to be completed when upgrading a Juju co…
Upgrading a k8s controller
juju upgrade-controller on k8s, the selection of the next JUju version to upgrade to is broken. As a work around, specify the version manually, eg
juju upgrade-controller --agent-version=2.8.2
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:
If you are upgrading Juju from 2.8.0 and have either a Kubernetes Juju controller or a Kubernetes Models the following steps will need to be performed
- 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
To prevent any confusion in later steps, ensure that you’re using the new Juju version.
What to do if Juju reports an old version
The controller state can be saved to allow for recovery in case the upgrade process encounters a serious error.
Juju includes a command that instructs the controller to upgrade itself to the latest version.
How to upgrade the controller
Your models remain at the same version until you have explicitly told Juju to upgrade them.
How to upgrade your model(s)
Juju’s documentation pages provide detailed information about the upgrade process:
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.