For the major upgrade from 4.0 to 4.1 use the JuJu charms upgrade path.
The charms will always install the latest version available of T4O 4.1. This will only work when upgrading from 4.0 to 4.1.
The following charms exist:
trilio-wlm Installs and manages Trilio Controller services.
trilio-dm-api Installs and manages the Trilio Datamover API service.
trilio-data-mover Installs and manages the Trilio Datamover service.
trilio-horizon-plugin Installs and manages the Trilio Horizon Plugin.
The documentation of the charms can be found here:
The following steps have been tested and verified within Trilio environments. There have been cases where these steps updated all packages inside the LXC containers, leading to failures in basic OpenStack services.
It is recommended to run each of these steps in dry-run first.
When any other packages but Trilio packages are getting updated, stop the upgrade procedure and contact your Trilio customer success manager.
Trilio is releasing hotfixes, which require updating the packages inside the containers. These hotfixes can not be installed using the Juju charms as they don't require an update to the charms.
Either 4.1 GA OR any hotfix patch against 4.1 should be already deployed for performing upgrades mentioned in the current document.
No snapshot OR restore to be running.
Global job scheduler should be disabled.
wlm-cron should be disabled ( Following commands are to be run on MAAS node)
If trilio-wlm is HA enabled, set the cluster configuration to maintenance mode ( this command will fail for single node deployment)
juju exec [-m <model>] --unit trilio-wlm/leader "sudo crm configure property maintenance-mode=true"
Stop wlm-cron service
juju exec [-m <model>] --application trilio-wlm "sudo systemctl stop wlm-cron"
Ensure that no stale wlm-cron processes are there
juju exec [-m <model>] --application trilio-wlm "sudo ps -ef | grep [w]orkloadmgr-cron"
If any stale process is found, that needs to be killed manually.
The mentioned gemfury repository should be accessible from trilio units.
The deployed Trilio version is controlled by the triliovault-pkg-source
charm configuration option.
For each trilio charm it should be pointing to below gemfury repository.
This can be checked via juju [-m ] config triliovault-pkg-source
command output.
This is the preferred, recommended and tested method to update the packages is through the Juju command line.
Run below commands form MASS node
Check the trilio units status in juju status [-m ] | grep trilio
output. All the trilio units will be with new package.
Run the below command to update the schema
Check the schema head with below command. It should point to latest schema head.
Run below command to restart the apache2 service on horizon container
If the trilio-wlm nodes are HA enabled:
Make sure the wlm-cron services are down after the pkg upgrade.
Run the following command for the same:juju exec [-m <model>] --application trilio-wlm "sudo systemctl stop wlm-cron"
Unset the cluster maintenance modejuju exec [-m <model>] --unit trilio-wlm/leader "sudo crm configure property maintenance-mode=false"
Make sure the wlm-cron service up and running on any one node.juju exec [-m <model>] --application trilio-wlm "sudo systemctl status wlm-cron"
Set the Global Job Scheduler to the original state.
If any trilio unit get into error state with message
hook failed: "update-status"
Follow below steps