WIP Juju 2.6.8 Release Notes


#1

The Juju team is proud to release Juju 2.6.8!

This is a primarily a bug fix release. All Juju users are advised to upgrade.

Highlights

This release includes several minor enhancements to cloud providers supported by Juju.

Updated vSphere vSAN support

Support for deploying workloads using vSAN storage volumes was delivered in 2.6.6 but didn’t work reliably in all cases. This has been addressed in this release.

New cloud regions

Support has been added for Azure regions:

  • South Africa North (azure/southafricanorth)
  • South Africa West (azure/southafricawest)
  • France South (azure/francesouth)

Suport has been added for the following AWS region:

  • Middle East (Bahrain) (aws/me-south-1)

New AWS instance types

Support has been added for the AWS bare metal instance types, such as i3.metal.

Important fixes include:

Bug ID Title
LP #1838774 ERROR cannot deploy bundle: cannot get model status: model not found
LP #1835770 charm stays in allocating state indefinitely
LP #1839918 k8s charm deployment type broken
LP #1838664 can’t set up k8s charm with no ports
LP #1838560 Missing relative path reference in bundle results in confusing error
LP #1838782 Destroying model fails initially, but works a second time
LP #1839918 k8s charm type field ignored in metadata.yaml

Additional bugs fixed can be found in the milestone page.

Acknowledgments

Thank you to the following contributors for providing your time for the benefit of the project:

  • Sean Shüping (@dvnt) for alerting us that the Azure regions were out of date
  • Frederik Nordahl Jul Sabroe for manually testing the vSAN fix
  • Casey Marshall (@cmars), Kenneth Koski (@knkski), Jason Hobbs (@jhobbs), Ian Booth (@wallyworld), Heather Lanigan (@hmlanigan), Tim McNamara (@timClicks) and Rick Harding (@rick_h) or filing bug reports

How to 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 installation options

Other packages are available for a variety of platforms, including Windows and macOS.

How to upgrade Juju

Upgrading a running Juju deployment takes 3 steps:

  1. Update the command-line client
  2. Upgrade your controller
  3. Upgrade your model(s)
Upgrading the Juju client

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

snap refresh juju 

If you’re using the PPA:

sudo apt update
sudo apt upgrade

On Homebrew for macOS:

brew update
brew upgrade
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
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

Feedback Appreciated!

We encourage everyone to let us know how you’re using Juju. Please ask questions on on Discourse, send us a message on Twitter using the hashtag #jujucharms, and chat with us at #juju on Freenode.


#2

#3