Release Juju 2.8.3 – Hotfix Release
Today, we are releasing Juju 2.8.3. This is a hotfix release for the 2.8 series, which addresses an issue upgrading from 2.8.1 to 2.8.2.
This release includes fixes to the following issues:
- LP #1895954 - SEGV when jujud restarts after upgrade-controller 2.8.1 -> 2.8.2
Fixing a broken 2.8.2 Upgrade
If you are experiencing a failure to upgrade, and find messages like this in your controller machine-*.log files, you are probably experiencing the issue:
panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x1d031ca] goroutine 460 [running]: github.com/juju/juju/state.ResetDefaultRelationLimitInCharmMetadata.
We have a workaround for people impacted by this bug.
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.