PowerVC rolling upgrade

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.

This topic explains the procedure for upgrading opsmgr utility and PowerVC on single node and multinode. You must have PowerVC 2.0.3 installed on RHEL 8.6 before proceeding with rolling upgrade. For direct installation procedure, see Initiate installation through PowerVC operations manager.

  • Legacy install of PowerVC is not supported for add node, replace node, resync node, compute plane node registration, and monitoring features.
  • PowerVC rolling upgrade can be performed on PowerVC 2.0.3 installed nodes.
  • Manually take a backup of existing PowerVC, before you upgrade opsmgr utility.
  • Before upgrading to PowerVC version 2.1.0, migrate any hosts running on Compute plane node to PowerVC controller by using /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST>. After upgrade process is completed, you can migrate the hosts back to Compute plane node by using /opt/ibm/powervc/bin/powervc-manage -o migratehmchost --hmchostname <MTMS HOST>.
  • If upgrade is interrupted at any point for various reasons, you can always re-trigger the upgrade procedure.
  • Until all three nodes in a multinode environment are upgraded, you will not be able use the GUI or API.
  • If upgrade for a remote node is being run, PowerVC OpsMgr will be upgraded automatically.
  • If network disconnections are expected, try to upgrade by using nohup command.
  • For multinode, the node hosting VIP must be upgraded in the end.
  • If there are any deploy failures post PowerVC update, it is recommended to restart PowerVC services and retry deploy operation.
  • To maintain PowerVC cluster consistency, restart controller node one at a time. Make sure that you allow 30 minutes before you restart the next node.

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:

    For ppc64le, extract download_location/powervc-opsmgr-<rhel or sles>-ppcle-2.1.0.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.1.0.tgz, where download_location is the directory where the tar file was downloaded to.

  3. Change the directory to: extract location/powervc-opsmgr-2.1.0, where extract location is the directory you extracted the tar file to in step 2. To upgrade from version 2.0.3 to 2.1.0, run update_opsmgr.sh script on the primary / 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.
  • For multinode, upgrade happens node by node.
  • Run powervc-opsmgr update --help for details on update sub-commands.
  • For single node environment, perform NovaLink upgrade to 2.1, before running powervc-opsmgr update command. For multinode environment, perform NovaLink upgrade after first node of PowerVC is upgraded.
  1. For single node upgrade, run powervc-opsmgr update -c <cluster_name> -n <node_ip/hostname> to upgrade PowerVC to version 2.1.0.
  2. Upgrade of multinode must be done one node at a time.

    Run powervc-opsmgr update -c <cluster_name> -n <node_ip/hostname> to upgrade non primary / bootstrap node.

Note: If monitoring is enabled before performing PowerVC upgrade , you must run powervc-opsmgr monitoring -c <cluster> --update to explicitly update monitoring and thereby update monitoring tools.

Monitoring scenario

Rolling upgrade is not supported by the monitoring scenario. Since Log Monitoring is not a mission-critical feature, this feature is not needed in production environments. So, before performing a rolling upgrade it is necessary to disable monitoring in the cluster inventory, by editing the corresponding /opt/ibm/powervc-opsmgr/ansible/inventory/<cluster_name>/group_vars/all/cluster.yam file. Change the value of the variable monitoring (if present) from true to false, then you may proceed with PowerVC rolling upgrade.

After the rolling upgrade is complete, refer to Monitoring scenario section in the topic Upgrading to PowerVC 2.1.0 for more information on how to upgrade your cluster's monitoring components.