Before you proceed with upgrading StackLight LMA, perform the following prerequisite steps:
Upgrade your MCP cluster as described in Upgrade DriveTrain to a newer release version.
Note
If you are performing a manitenance update, verify that you have updated your MCP cluster as described in Update DriveTrain instead.
Log in to the Salt Master node.
Verify that there are no uncommitted changes on the cluster and system levels of the Reclass model:
For the cluster level:
cd /srv/salt/reclass/classes/cluster/<cluster_name>/
git status
For the system level:
cd /srv/salt/reclass/classes/system
git status
Example of system response:
On branch <branch_name>
Your branch is up-to-date with 'origin/<branch_name>'.
nothing to commit, working tree clean
In case of any uncommitted changes, solve the issue before proceeding with the upgrade.
Verify that all Salt minions are available:
salt '*' test.ping
Example of system response:
cmp0.<cluster_name>:
True
mon01.<cluster_name>:
True
gtw01.<cluster_name>:
True
mon02.<cluster_name>:
True
prx01.<cluster_name>:
True
cmp1.<cluster_name>:
True
mon03.<cluster_name>:
True
cfg01.<cluster_name>:
True
If any VM is not available, do not proceed before resolving the issue.
Verify that no alerts are triggered in the Alertmanager web UI as described in Use the Alertmanager web UI.
Caution
If any alert is triggered, investigate the issue before proceeding with the upgrade. An alert may have a low severity and it is up to the system administrator to decide whether to proceed with the upgrade in this case.
Specify the elasticsearch_version: 6
and kibana_version: 6
parameters in the classes/cluster/<cluster_name>/stacklight/log.yml
file
of your Reclass model to upgrade Elasticsearch and Kibana from v5 to v6.
Otherwise, Elasticsearch and Kibana will be upgraded to the latest minor
stable versions.
Once done, proceed to Upgrade StackLight LMA using the Jenkins job.