Skip to main content

Your submission was sent successfully! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates from Canonical and upcoming events where you can meet our team.Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

Upgrade Juju for a new database revision

This guide contains instructions to perform a patch or major/minor Juju upgrade to a controller and model containing a database charm.

For more background about Juju upgrades in the context of database charms, check Explanation > Juju > Juju upgrades.

Summary

Patch version upgrade

A PATCH Juju upgrade (e.g. Juju 3.1.5 → 3.1.8) can be easily applied in-place.

sudo snap refresh juju 

juju upgrade-controller 
# wait until complete

juju upgrade-model 
# wait until complete

Once the model has finished upgrading, you can proceed with the charm upgrade.

Major/minor version upgrade

The easiest way to perform a MAJOR/MINOR Juju version upgrade (e.g. Juju 3.1.8 → 3.5.1), is to update the controller and model to the new version, then migrate the model.

Commands summary

The following is a summary of commands that upgrade Juju to 3.5/stable:

sudo snap refresh juju --channel 3.5/stable

juju bootstrap lxd lxd_3.5.1 # --agent-version 3.5.1

juju migrate lxd_3.1.8:mydatabase lxd_3.5.1

juju upgrade-model -m lxd_3.5.1:mydatabase 
# wait until complete

Once the model has finished upgrading, you can proceed with the charm upgrade.

Example

This section goes over the commands listed in the summary above with more details and sample outputs.

In this example scenario, we have mysql deployed in model mydatabase on the Juju controller lxd_3.1.8. 
juju status

Model       Controller  Cloud/Region         Version  SLA          Timestamp
mydatabase  lxd_3.1.8   localhost/localhost  3.1.8    unsupported  22:54:48+02:00

App    Version          Status  Scale  Charm  Channel     Rev  Exposed  Message
mysql  8.0.34-0ubun...  active      3  mysql  8.0/stable  196  no       

Unit      Workload  Agent  Machine  Public address  Ports           Message
mysql/0*  active    idle   0        10.217.68.104   3306,33060/tcp  Primary
mysql/1   active    idle   1        10.217.68.118   3306,33060/tcp  
mysql/2   active    idle   2        10.217.68.144   3306,33060/tcp  

Machine  State    Address        Inst id        Base          AZ  Message
0        started  10.217.68.104  juju-a4598a-0  ubuntu@22.04      Running
1        started  10.217.68.118  juju-a4598a-1  ubuntu@22.04      Running
2        started  10.217.68.144  juju-a4598a-2  ubuntu@22.04      Running

To upgrade Juju to v.3.5.1, we go through the following steps:

1. Update the Juju CLI

Check the current version with the command:

 juju --version

Perform the upgrade:

sudo snap refresh juju --channel 3.5/stable

Optionally rerun the juju --version command to confirm the upgrade.

2. Bootstrap the new controller

Use the juju bootstrap command to create a new controller. In this example, we specify a particular version (and name the controller accordingly):

juju bootstrap lxd lxd_3.5.1 --agent-version 3.5.1

This will produce output describing progress and the steps taken, similar to:

Creating Juju controller "lxd_3.5.1" on lxd/localhost
Looking for packaged Juju agent version 3.5.1 for amd64
Located Juju agent version 3.5.1-ubuntu-amd64 at https://streams.canonical.com/juju/tools/agent/3.5.1/juju-3.5.1-linux-amd64.tgz
To configure your system to better support LXD containers, please see: https://documentation.ubuntu.com/lxd/en/latest/explanation/performance_tuning/
Launching controller instance(s) on localhost/localhost...
 - juju-374723-0 (arch=amd64)          
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to 10.217.68.44:22
Connected to 10.217.68.44
Running machine configuration script...
Bootstrap agent now started
Contacting Juju controller at 10.217.68.44 to verify accessibility...
Bootstrap complete, controller "lxd_3.5.1" is now available
Controller machines are in the "controller" model
...
3. Migrate the entire model mydatabase to the new controller (no database outage here) 
~$ juju controllers
Controller  Model       User   Access     Cloud/Region         Models  Nodes    HA  Version
lxd_3.1.8*  mydatabase  admin  superuser  localhost/localhost       2      1  none  3.1.8  
lxd_3.5.1   -           admin  superuser  localhost/localhost       1      1  none  3.5.1

~$ juju models -c lxd_3.1.8
Controller: lxd_3.1.8
Model        Cloud/Region         Type  Status     Machines  Units  Access  Last connection
controller   localhost/localhost  lxd   available         1      1  admin   just now
mydatabase*  localhost/localhost  lxd   available         3      3  admin   36 seconds ago

~$ juju models -c lxd_3.5.1
Controller: lxd_3.5.1
Model       Cloud/Region         Type  Status     Machines  Units  Access  Last connection
controller  localhost/localhost  lxd   available         1      1  admin   just now

~$ juju migrate lxd_3.1.8:mydatabase lxd_3.5.1
Migration started with ID "5f227519-3cdb-4538-871c-1c4589a4598a:0"
4. Use juju models to check the migration process has started ( model status=busy). At the end of the process, the model is no longer available on the old controller as it has been moved to new controller 
~$ juju models --controller lxd_3.1.8
...
mydatabase*  localhost/localhost  lxd   busy              3      3  admin   1 minute ago

~$ juju models --controller lxd_3.1.8
Controller: lxd_3.1.8
Model       Cloud/Region         Type  Status     Machines  Units  Access  Last connection
controller  localhost/localhost  lxd   available         1      1  admin   just now

~$ juju models --controller lxd_3.5.1
Controller: lxd_3.5.1
Model       Cloud/Region         Type  Status     Machines  Units  Access  Last connection
controller  localhost/localhost  lxd   available         1      1  admin   just now
mydatabase  localhost/localhost  lxd   available         3      3  admin   1 minute ago
5. Upgrade the model version itself (no database outage here) 
> juju status -m lxd_3.5.1:mydatabase
Model       Controller  Cloud/Region         Version  SLA          Timestamp
mydatabase  lxd_3.5.1   localhost/localhost  3.1.8    unsupported  22:58:10+02:00
...

> juju upgrade-model -m lxd_3.5.1:mydatabase
best version:
    3.5.1
started upgrade to 3.5.1

> juju status -m lxd_3.5.1:mydatabase
Model       Controller  Cloud/Region         Version  SLA          Timestamp
mydatabase  lxd_3.5.1   localhost/localhost  3.5.1    unsupported  22:59:01+02:00
...

At this stage, the application continues running under the supervision of the new controller version and is ready to be refreshed to the new charm revision.

You can now proceed with the charm upgrade.

Resources

Further documentation about Juju upgrades:

Previous Upgrade Next Perform a minor upgrade

Last updated 2 months ago. Help improve this document in the forum.