Upgrade IBM Spectrum Fusion HCI 2.2.1 to 2.3

As an administrator user, upgrade components of IBM Spectrum Fusion HCI from 2.2.1 to 2.3. The IBM Spectrum Fusion HCI upgrade involves software and firmware.

Before you begin

Prechecks
Run the following command to check whether the Scale CR (storagemanager) reports the cluster as healthy: 
oc -n ibm-spectrum-fusion-ns get scales storagemanager -oyaml | grep storageClusterStatus
The output of the command must be healthy. If it shows as DEGRADED, then resolve the issue and then proceed with the upgrade.
Note: If the IBM Spectrum Scale is not healthy, do not initiate the upgrade. Check events to get further details about the problem. Contact IBM support in case the issue cannot be resolved.
Setup enterprise registry
If you installed the earlier version of IBM Spectrum Fusion HCI by using your enterprise registry, then see Prerequisites for your enterprise registry.

About this task

Do the upgrade in the specified sequence.

Procedure

  1. Upgrade IBM Spectrum Fusion HCI management software. For the actual steps to upgrade, see Upgrading IBM Spectrum Fusion HCI management software from 2.2.1 to 2.3.
  2. Upgrade the Global data platform (storage) service. For more information about upgrade, see Upgrading services.
  3. Upgrade the Global protection (backup and restore) service. For the actual steps to upgrade, see Upgrading services.
  4. Upgrade node firmware. For actual steps to upgrade, see Upgrading node firmware.
  5. Upgrade switch firmware. For actual steps to upgrade, see Upgrading switch firmware.
  6. Upgrade Red Hat® OpenShift Container Platform from Red Hat OpenShift Container Platform.
    Note: The Red Hat OpenShift Container Platform version must be upgraded only to the version supported by IBM Spectrum Fusion HCI. Do not upgrade or rollback your Red Hat OpenShift Container Platform version manually until the support is included in IBM Spectrum Fusion HCI.
    Upgrade Red Hat OpenShift Container Platform to 4.9 first and then upgrade to 4.10. There is no direct upgrade path from Red Hat OpenShift Container Platform 4.8 to 4.10.
    1. Before you upgrade to Red Hat OpenShift Container Platform 4.10, follow the steps mentioned in this Red Hat article. These steps are required so that the bond configuration for Open Shift cluster is healthy and reconfigured successfully during 4.10 upgrade.
    2. Remove the extra nmconnection files from core OS nodes for interfaces that do not exist in the node. Refer to the following table for list of files to be deleted for different types of nodes.
         
      Storage
      • ens6f1.nmconnection
      • ens6f0.nmconnection
      • ens2f1.nmconnection
      • ens2f0.nmconnection
      AFM
      • ens6f1.nmconnection
      • ens6f0.nmconnection
      • ens1f1.nmconnection
      • ens1f0.nmconnection
      GPU
      • ens1f1.nmconnection
      • ens1f0.nmconnection
      • ens2f1.nmconnection
      • ens2f0.nmconnection
      For example, remove the following four files from the Core OS filesystem /etc/NetworkManager/system-connections directory for storage nodes: 
      
[root@compute-0 system-connections]# pwd
/etc/NetworkManager/system-connections
[root@compute-0 system-connections]# ls -lrt
total 88
-rw-------. 1 root root 114 Sep 21 09:48 ens6f1.nmconnection
-rw-------. 1 root root 114 Sep 21 09:48 ens6f0.nmconnection
-rw-------. 1 root root 114 Sep 21 09:48 ens2f1.nmconnection
-rw-------. 1 root root 114 Sep 21 09:48 ens2f0.nmconnection
    For the actual procedure to upgrade Red Hat OpenShift Container Platform, see https://docs.openshift.com/container-platform/4.10/updating/understanding-openshift-updates.html.
    Note: The target 4.10 version of Red Hat OpenShift Container Platform must be 4.10.30 or higher.
  7. Optionally, upgrade Red Hat and Community operators. For actual steps to upgrade, see Upgrade Red Hat and Community Operators.

What to do next

  • For all the backup and restore jobs to be successful post upgrade, run the following commands to delete Kafka and Apache Zookeeper pods: 
    
oc delete pod baas-kafka-0 -n baas
oc delete pod baas-zookeeper-0 -n baas
oc delete pod baas-zookeeper-1 -n baas
oc delete pod baas-zookeeper-2 -n baas

    After you run these commands, wait for the pods to restart.

  • Before you add new nodes to the upgraded IBM Spectrum Fusion HCI OpenShift Container Platform 4.10 cluster, the machine set on the cluster must be modified. For the procedure to modify, see Manual migration to new customDeploy install method.
  • Post upgrade procedure for logs and Call Home. For the steps, see Post upgrade procedure for logs and Call Home.
  • Before you proceed to work with IBM Spectrum Fusion HCI, go through the known issues and troubleshooting mentioned in Troubleshooting upgrade issues.