Upgrade Management Node

This section uses H84r as an example to introduce a step-by-step guide for upgrading a single management node environment.

Procedure

Check the current environment version and the operating system version.

[root@localhost ~]# zstack-ctl status
[root@localhost ~]# cat /etc/readhat-release

Obtain the upgrade packages.
Download the zstack-upgrade script, ISO software package, upgrade packages, and the HA suite for management node as needed.
Disable the HA policy.
Before the upgrade, you need to disable the global switch for virtual machine high availability to avoid triggering it accidentally, which could affect the upgrade. After the upgrade is complete, manually enable the HA policy.
1. Log in to ZStack ZSphere.
2. Click Business Reliability > HA Policy to enter the HA Policy page.
3. Disable the HA policy switch.

Back up the database and upgrade script.

Log in to the management node system and then run the following commands to back up the database and upgrade script for emergency recovery:

# Back up the database to the /var/lib/zstack/mysql-backup/ directory
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup

# Back up the upgrade script to the /root/ directory
[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk

Upgrade ZStack ZSphere.

# Two offline upgrade methods are supported. The first method is recommended.
# Method 1: Upgrade the local repository and management services
[root@zstack-1 opt]# zstack-upgrade ZStack-ZSphere-x86_64-DVD-5.0.3-H84r.iso

# Method 2: First upgrade the local repository and then upgrade the management services
[root@zstack-1 opt]# zstack-upgrade -r ZStack-ZSphere-x86_64-DVD-5.0.3-H84r.iso 
[root@zstack-1 opt]# bash ZStack-ZSphere-installer-5.0.3.bin -u -P MYSQL_ROOT_PASSWORD

Note:

If the database root password uses the system default password zstack.mysql.password, you can omit the -P MYSQL_ROOT_PASSWORD parameter.
Before executing the zstack-upgrade command, ensure that the prepared ISO is based on version H84r to avoid using other ISOs that may overwrite the local source.

Clear the browser cache.
To ensure that the new features work properly, it is recommended that after the upgrade is complete, you log in to the UI management interface and manually clear the browser cache by pressing Ctrl+F5 or Ctrl+Shift+R.
Enable the HA policy.

Upgrade MN HA Environment

This section uses H84r as an example to introduce a step-by-step guide for upgrading a management node environment that has HA configured.

Procedure

Check the current environment version and the operating system version.

[root@localhost ~]# zstack-ctl status
[root@localhost ~]# cat /etc/readhat-release

Obtain the upgrade packages.
Download the zstack-upgrade script, ISO software package, upgrade packages, and the HA suite for management node as needed.
Disable the HA policy.
Before the upgrade, you need to disable the global switch for virtual machine high availability to avoid triggering it accidentally, which could affect the upgrade. After the upgrade is complete, manually enable the HA policy.
1. Log in to ZStack ZSphere.
2. Click Business Reliability > HA Policy to enter the HA Policy page.
3. Disable the HA policy switch.

Back up the database and upgrade script.

Log in to the management node system and then run the following commands to back up the database and upgrade script for emergency recovery:

# Back up the database to the /var/lib/zstack/mysql-backup/ directory
[root@localhost ~]# zstack-ctl dump_mysql --file-name zstack-db-backup

# Back up the upgrade script to the /root/ directory
[root@localhost ~]# cp /usr/local/bin/zstack-upgrade /root/zstack-upgrade-bk

Obtain the IP address of the management node where the VIP is located.
Run the following command to obtain the IP address of the management node where the VIP is located. The node with VIP marked as yes in the returned results is the management node where the VIP is located:
```
[root@localhost ~]# zsha2 status
```
Unpack the HA suite and grant executable permission.
On the management node where the VIP is located, run the following commands in sequence to unpack the HA suite and grant executable permissions to the zsha2 and zstack-hamon files:
```
# Unpack the HA suite
[root@localhost ~]# tar zxvf ZStack-ZSphere-Multinode-HA-Suite.tar.gz

# Grant executable permissions
[root@localhost ~]# chmod +x zsha2 zstack-hamon
```
Upgrade the HA suite.
On the management node where the VIP is located, run the following command to upgrade the HA suite:
```
[root@localhost ~]# ./zsha2 upgrade-ha
```
Run the zsha2 version command to check if the commit id matches the one in the latest version package.
Upgrade ZStack-ZSphere.
On the management node where the VIP is located, run the following command to upgrade the virtualization platform:
```
zsha2 upgrade-mn -peerpass password ZStack-ZSphere-x86_64-DVD-5.0.3-H84r.iso
```
Note: -peerpass is optional and can be set to the SSH login password for the peer management node.
Clear the browser cache.
To ensure that the new features work properly, it is recommended that after the upgrade is complete, you log in to the UI management interface and manually clear the browser cache by pressing Ctrl+F5 or Ctrl+Shift+R.
Enable the HA policy.