Upgrading IBM Storage Fusion

Procedure to upgrade IBM Storage Fusion to 2.5.1 or 2.5.2. You can also follow these steps to upgrade from 2.5.1 to 2.5.2.

Before you begin

Ensure that you are on IBM Storage Fusion version 2.4.
If you installed IBM Storage Fusion version 2.4 by using online or your enterprise registry installation mode, then ensure that you do not change the mode during the upgrade to 2.5.1 version. To change the installation mode, reinstall IBM Storage Fusion 2.5.1 or 2.5.2.
Ensure all compute nodes are in ready state on OpenShift® user interface.
Ensure node upsize and disk scale out are not initiated until upgrade is complete.
Logs that you collected by using the IBM Storage Fusion Collect logs user interface page gets deleted after the upgrade process completes. Download the needed logs before you begin the upgrade.

Setup enterprise registry

If you installed the earlier version of IBM Storage Fusion by using your enterprise registry, then follow the steps to mirror images in your enterprise registry.

Mirror IBM Storage Fusion, IBM Spectrum Scale, IBM Spectrum Protect Plus, Backup & Restore, IBM Storage Fusion Data Foundation and Data Cataloging images. For steps to mirror, see Mirroring your images to the enterprise registry.
Update the global pull secret with the mirror registry credentials to which the current version images are mirrored. Ignore this step, if you are mirroring to the same enterprise registry that you used for the previous version.

In the IBM Storage Fusion namespace, create a new key/value secret named user-install-secret using the following content.

For example 2.5.1:

{
isfimagepath: <path to the mirrored images within the regsitry>   
 isfregistry: <isf-enterprise-registry>:<port>
 isfregistrypassword: <enterprise registry password>
 isfregistryuser: <enterprise registry user name>
 isPrivateRegistry: true
}

See the following user-install-secret sample for 2.5.1:

kind: Secret
apiVersion: v1
metadata:
  name: user-install-secret
  namespace: ibm-spectrum-fusion-ns
data:
    isfregistry: <enterprise registry host:enterprise registry port>
    isfimagepath: <isf 2.5.1 mirror path>
    isfregistryuser: <enterprise registry user name>
    isfregistrypassword: <enterprise registry password>
    isPrivateRegistry: true

Modify the image content source policy isf-operator-index to add the new mirror that points to the new registry for each source defined in the image content source policy. Ignore this step, if you are mirroring to the same enterprise registry as the previous version.

See the sample image content source policy for 2.4 to 2.5.1 upgrade path:

apiVersion: operator.openshift.io/v1alpha1
kind: ImageContentSourcePolicy
metadata:
  name: isf-catalog-index
spec:
  repositoryDigestMirrors:
  # for scale
  - mirrors:
    - <ISF 2.4 enterprise registry host>/<ISF 2.4 target-path>
    - <ISF 2.4 enterprise registry host:port>/<ISF 2.4 target-path>
    - <ISF 2.5.1 enterprise registry host>/<ISF 2.5.1 target-path>
    - <ISF 2.5.1 enterprise registry host:port>/<ISF 2.5.1 target-path>
    source: cp.icr.io/cp/spectrum/scale
  - mirrors:
    - <ISF 2.4 enterprise registry host>/<ISF 2.4 target-path>
    - <ISF 2.4 enterprise registry host:port>/<ISF 2.4 target-path>
    - <ISF 2.5.1 enterprise registry host>/<ISF 2.5.1 target-path>
    - <ISF 2.5.1 enterprise registry host:port>/<ISF 2.5.1 target-path>
    source: icr.io/cpopen
  #for IBM Spectrum Fusion operator 
  - mirrors:
    - <ISF 2.4 enterprise registry host>/<ISF 2.4 target-path>
    - <ISF 2.4 enterprise registry host:port>/<ISF 2.4 target-path>
    - <ISF 2.5.1 enterprise registry host>/<ISF 2.5.1 target-path>
    - <ISF 2.5.1 enterprise registry host:port>/<ISF 2.5.1 target-path>
    source: cp.icr.io/cp/isf-sds
  # for spp agent
  - mirrors:
    - <ISF 2.4 enterprise registry host>/<ISF 2.4 target-path>/sppc
    - <ISF 2.4 enterprise registry host:port>/<ISF 2.4 target-path>/sppc
    - <ISF 2.5.1 enterprise registry host>/<ISF 2.5.1 target-path>/sppc
    - <ISF 2.5.1 enterprise registry host:port>/<ISF 2.5.1 target-path>/sppc
    source: cp.icr.io/cp/sppc
  - mirrors:
    - <ISF 2.4 enterprise registry host>/<ISF 2.4 target-path>/sppc
    - <ISF 2.4 enterprise registry host:port>/<ISF 2.4 target-path>/sppc
    - <ISF 2.5.1 enterprise registry host>/<ISF 2.5.1 target-path>/sppc
    - <ISF 2.5.1 enterprise registry host:port>/<ISF 2.5.1 target-path>/sppc
    source: registry.redhat.io/amq7
  - mirrors:
    - <ISF 2.4 enterprise registry host>/<ISF 2.4 target-path>/sppc
    - <ISF 2.4 enterprise registry host:port>/<ISF 2.4 target-path>/sppc
    - <ISF 2.5.1 enterprise registry host>/<ISF 2.5.1 target-path>/sppc
    - <ISF 2.5.1 enterprise registry host:port>/<ISF 2.5.1 target-path>/sppc
    source: registry.redhat.io/oadp

About this task

Use this procedure for the following IBM Storage Fusion upgrade paths:

2.4 version to 2.5.1
2.4 version to 2.5.2
2.5.1 to 2.5.2

Procedure

Log in to the OpenShift Container Platform management console as the cluster administrator.
Upgrade IBM Storage Fusion on On-premises VMware, On-premises Bare Metal, or Amazon Web Services as follows:
1. From the navigation menu, click Operators > Installed Operators.
2. From the Installed Operators list, click IBM Storage Fusion operator.
  The Details tab opens by default.
3. Go to Subscription tab.
4. View the Subscription details section for the upgrade status.
  
  Note: If this is an offline setup, then update the image path in IBM Storage Fusion catalog source with new catalog source image.
5. If an upgrade is available for the operator, then click Approve to manually initiate the upgrade. If you do not agree to the upgrade, click Deny.
  If no new upgrade is available, then Upgrade status displays Up to date.
  Note: By default, the upgrade of the IBM Storage Fusion is Automatic. However, you can change it to Manual.
6. After the upgrade is successful, refresh your browser and clear your cache.
7. Verify whether the IBM Storage Fusion is in succeeded state and the version is 2.5.1 or 2.5.2. Also, in the Subscription tab, ensure that the upgrade status displays Up to date.
Upgrade IBM Storage Fusion services.
For the steps to upgrade services, see Upgrading IBM Storage Fusion services.
Upgrade Red Hat® OpenShift Container Platform from Red Hat OpenShift Container Platform console.

Note: The Red Hat OpenShift Container Platform version must be upgraded only to the version supported by IBM Storage Fusion. Do not upgrade or rollback your Red Hat OpenShift Container Platform version manually until the support is included in IBM Storage Fusion.

If you are on Red Hat OpenShift Container Platform 4.10, and you want to use Red Hat OpenShift Container Platform 4.12, first upgrade to 4.11 and then upgrade to 4.12. There is no direct upgrade path from Red Hat OpenShift Container Platform 4.10 to 4.12. For the actual procedure to upgrade Red Hat OpenShift Container Platform, see Understanding OpenShift Container Platform updates.

What to do next

When you upgrade from 2.5.1 to 2.5.2, manually upgrade the IBM Spectrum Protect Plus agent:

To start IBM Spectrum Protect Plus upgrade, set triggerUpgrade to true:

fusionns=$(oc get spectrumfusions.prereq.isf.ibm.com -A -o=custom-columns=CR_NAME:.metadata.namespace --no-headers)
oc patch -p '{"spec":{"triggerUpgrade":true}}' --type=merge sppmanager/sppmanager -n $fusionns