Upgrade the Management Node HA Environment

This task applies to a ZSphere environment where management node HA is configured.

• Before performing this task, complete Prepare for Upgrade.
• Perform the upgrade during a maintenance window. Management services must be stopped on both nodes during the upgrade. By default, the HA suite upgrade also restarts the databases on both nodes. The management UI and management services will be temporarily unavailable.

Note: Before upgrading a production environment, we recommend that you contact technical support to confirm the upgrade plan and related precautions.

1. Obtain the IP address of the management node where the VIP resides.
   Run the following command to obtain the IP address of the management node where the VIP resides. In the returned results, the node whose VIP value is yes is the management node where the VIP resides.

   [root@localhost ~]# zsha2 status

2. Unpack the HA suite and grant executable permissions.
   On the management node where the VIP resides, 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

3. Stop management services on both nodes.
   Log in to each management node and run the following command to stop management services.

   [root@localhost ~]# zsha2 stop-node

4. Upgrade the HA suite.
   On the management node where the VIP resides, run the following command from the directory where the HA suite was unpacked.

   [root@localhost ~]# ./zsha2 upgrade-ha

   Note:

   • Make sure management services are stopped on both nodes. Otherwise, the upgrade cannot proceed.
   • The gencfg parameter defaults to true and does not need to be specified explicitly. The upgrade updates the database configuration and restarts MariaDB on both nodes.
   • If you explicitly specify -gencfg=false, the database configuration update and the corresponding MariaDB restart are skipped. Fixes that depend on the configuration update will not take effect. For a regular upgrade, use the command above without specifying this parameter.
5. Run the zsha2 version command to check whether the commit id matches the one in the latest version package.
6. Upgrade ZStack-ZSphere.
   On the management node where the VIP resides, run the following command to upgrade the virtualization platform.

   zsha2 upgrade-mn -peerpass password ZStack-ZSphere-x86_64-DVD-5.2.0-H84r.iso

   Note: -peerpass is optional. You can use it to specify the SSH login password of the peer management node.