PowerVC offline upgrade

Edit online

The PowerVC Operations Manager (OpsMgr) is a collection of utilities and services that are designed to facilitate user operation of PowerVC clusters like install, upgrade, backup, and restore. In a multinode (HA) environment, all nodes can now be updated while services are offline. Update happens simultaneously on all nodes.

This topic explains the procedure for offline upgrading of opsmgr utility and PowerVC on single node and multinode.

For RHEL
  • You can upgrade to PowerVC 2.3.1 from PowerVC 2.2.1, 2.2.1.1, 2.2.1.2, or 2.3.0 by using the PowerVC offline upgrade procedure.
  • You must have PowerVC 2.2.1, 2.2.1.1, 2.2.1.2, or 2.3.0 installed on the supported RHEL 8.x and 9.x version before proceeding with offline upgrade to PowerVC for Private Cloud 2.3.1. For direct installation procedure, see Initiate installation through PowerVC operations manager.
For SLES
  • You can upgrade to PowerVC 2.3.1 from PowerVC 2.2.1, 2.2.1.1, 2.2.1.2, or 2.3.0 by using the PowerVC offline upgrade procedure.
  • You must have PowerVC 2.2.1, 2.2.1.1, 2.2.1.2, or 2.3.0 installed on the supported SLES 15 SP5 version before proceeding with offline upgrade to PowerVC for Private Cloud 2.3.1. For direct installation procedure, see Initiate installation through PowerVC operations manager.

Prerequisites

Notes:
  • Manually take a backup of existing PowerVC, before you upgrade opsmgr utility.
  • Before you upgrade to PowerVC version 2.3.1, migrate any hosts that runs on Compute plane node to PowerVC controller by using the /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST> command. After upgrade process is complete, you can migrate the hosts back to Compute plane node by using the /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST> command.
Notes:
  • If upgrade is interrupted at any point for various reasons, you can always re-trigger the upgrade procedure.
  • If network disconnections are expected, try to upgrade by using nohup command.
  • PowerVC is not accessible when upgrade is in progress.

Upgrading opsmgr utility

  1. Visit Fix Central to download and install any fix packs that are available. For more information see the Getting fixes from Fix Central topic.
  2. Extract the tar file that matches your environment to the location you want to run the installation script from:
    • Upgrading to PowerVC 2.3.1 from PowerVC 2.2.1, 2.2.1.1, 2.2.1.2, or 2.3.0 versions

      For ppc64le, extract download_location/powervc-opsmgr-<rhel or sles>-ppcle-2.3.1.tgz, where download_location is the directory where the tar file was downloaded to.

      For x86_64, extract the download_location/powervc-opsmgr-rhel-x86-2.3.1.tgz, where download_location is the directory where the tar file was downloaded to.

  3. Change the directory to: extract location/powervc-opsmgr-2.3.1, where extract location is the directory you extracted the tar file to in step 2.
  4. Run the following pre-update opsmgr health check command before you perform the update opsmgr operation:
    python3 powervc_opsmgr_health_check.py
  5. To upgrade from 2.2.1, 2.2.1.1, 2.2.1.2, or 2.3.0 versions to 2.3.1, run update_opsmgr.sh script on the primary or bootstrap node.

    Alternatively, you can run <path>/update_opsmgr.sh -s to perform silent installation.

Upgrading PowerVC on single node or multinode

After upgrading OpsMgr, you can upgrade PowerVC on single node and later add multiple nodes (up to five nodes) if needed.
Notes:
You must run the powervc-health-check update command before you perform the update operation. For more information about the health check commands, see the powervc-health-check command in the CLI commands page. After the update health check is complete run the powervc-opsmgr update -o/--offline-mode -c/--cluster <cluster_name> command on primary / bootstrap node to upgrade.
Notes:
  • If there are any deploy failures post PowerVC update, it is recommended to restart PowerVC services and retry deploy operation.
  • After the upgrade is complete, and you see the host state as unknown, check if IPv6 is enabled in the node by running the sysctl -a 2>/dev/null | grep disable_ipv6 command. If IPv6 is enabled, disable IPv6 in all the nodes by running the sudo sysctl -w -p net.ipv6.conf.all.disable_ipv6=1 command, and then reboot the system.
  • Occasionally, after an upgrade, the virtual IP might become unreachable. You can confirm if the virtual IP is reachable or not by a ping test. This issue might occur due to an IP conflict or high load during the upgrade. If this issue occurs, run crm_resource -r virtualip --restart command after the upgrade to reactivate the virtual IP.