Upgrading IBM Storage Fusion

Procedure to upgrade IBM Storage Fusion to 2.6 or 2.6.1.

Before you begin

  • For 2.6.1, ensure that you are on 2.6 version. For 2.6, ensure that you are on IBM Storage Fusion version 2.5.2.
  • If you installed IBM Storage Fusion version 2.5.x by using online or your enterprise registry installation mode, then ensure that you do not change the mode during the upgrade to 2.6 version. To change the installation mode, reinstall 2.6.
  • If you installed IBM Storage Fusion version 2.6 by using online or your enterprise registry installation mode, then ensure that you do not change the mode during the upgrade to 2.6.1 version. To change the installation mode, reinstall 2.6.1.
  • 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. If you are mirroring to the same enterprise registry that you used for the previous version, then ignore this step.
    • Data Cataloging offline upgrade:
      1. Complete steps 1 to 8 of Mirroring Data Cataloging images procedure.
      2. Update the redhat-operators catalog source.
        apiVersion: operators.coreos.com/v1alpha1
        kind: CatalogSource
        metadata:
          name: redhat-operators-data-cataloging
          namespace: openshift-marketplace
        spec:
          displayName: Red Hat Operators for Data Cataloging
          image: "$PRUNED_RED_HAT_OPERATORS_IMAGE"
          sourceType: grpc
          updateStrategy:
            registryPoll:
              interval: 15m
      3. If a new TARGET_PATH value is used for the upgrade, then update the existing ImageContentSourcePolicy.
        apiVersion: operator.openshift.io/v1alpha1
        kind: ImageContentSourcePolicy
        metadata:
          labels:
            operators.openshift.org/catalog: "true"
          name: isd-mirror
        spec:
          repositoryDigestMirrors:
          - mirrors:
            - $TARGET_PATH
            source: icr.io/cpopen
          - mirrors:
            - $TARGET_PATH
            source: registry.redhat.io/redhat
          - mirrors:
            - $TARGET_PATH/amq
            - $TARGET_PATH
            source: registry.redhat.io/amq7
          - mirrors:
            - $TARGET_PATH/ibm-spectrum-discover
            source: cp.icr.io/cp/ibm-spectrum-discover
          - mirrors:
            - $TARGET_PATH/db2u
            source: icr.io/db2u
    • Offline upgrade of Data Foundation images deployed on OpenShift Container Platform version 4.12:
      1. Complete steps 1 to 7 of Mirroring Data Foundation images deployed on OpenShift Container Platform version 4.12 topic.
      2. Before you upgrade IBM Storage Fusion, from the Services page of the IBM Storage Fusion user interface, disable Automatic updates for Data Foundation service.
      3. Go to Operators > Installed Operators > IBM Storage Fusion Data Foundation > Subscription, and check whether the Update approval is changed to Manually.
      4. Start the IBM Storage Fusion version upgrade.
      5. Update the image digest ID after you upgrade the IBM Storage Fusion as follows:
        1. Run the following command to get the catalog source image digest ID.
          skopeo inspect docker://<enterprise registry host:port>/<target-path>/cpopen/isf-data-foundation-catalog:v4.12 | jq -r ".Digest"
          

          You need to record the image digest ID. It is used in deployment phase only.

        2. Ensure that the data-foundation-service FusionServiceDefinition CR is created.
          oc get fusionservicedefinitions.service.isf.ibm.com -n ibm-spectrum-fusion-ns data-foundation-service
          
        3. Update the imageDigest in the FusionServiceDefinition data-foundation-service.
          skopeo inspect docker://<enterprise registry host:port>/<target-path>/cpopen/isf-data-foundation-catalog:v4.12 | jq -r ".Digest"
          
        4. Edit the data-foundation-service .spec.onboarding.serviceOperatorSubscription.multiVersionCatSrcDetails.ocp412-t.imageDigest.
          oc edit fusionservicedefinitions.service.isf.ibm.com -n ibm-spectrum-fusion-ns data-foundation-service
          
          Example output:
          spec:
            hasRelatedDefinition: false
            onboarding:
          ...
              serviceOperatorSubscription:
                catalogSourceName: isf-data-foundation-catalog
                createCatalogSource: true
                globalCatalogSource: true
                isClusterWide: false
                multiVersionCatSrcDetails:
                  ocp49:
                    skipCatSrcCreation: true
                  ocp410:
                    skipCatSrcCreation: true
                  ocp411:
                    skipCatSrcCreation: true
                  ocp412-t:
                    displayName: Data Foundation Catalog
                    imageDigest: sha256:ed94a66296d1a4fe047b0a79db0e8653e179a8a2a646b0c05e435762d852de73
                    imageName: isf-data-foundation-catalog
                    imageTag: v4.12
                    publisher: IBM
                    registryPath: icr.io/cpopen
                    skipCatSrcCreation: false
      6. Change Update approval to the original value in IBM Storage Fusion user interface.
    • In the IBM Storage Fusion namespace, create a new key/value secret named user-install-secret using the following content.

      For example 2.6.1:

      Note: This step is applicable for IBM Storage Fusion, Global Data Platform, and Backup & Restore (Legacy).
      {
      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.6.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.6.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 older version to newer version upgrade path:
      apiVersion: operator.openshift.io/v1alpha1
      kind: ImageContentSourcePolicy
      metadata:
        name: isf-catalog-index
      spec:
        repositoryDigestMirrors:
        # for scale
        - mirrors:
          - <Old ISF enterprise registry host>/<Old ISF target-path>
          - <Old ISF enterprise registry host:port>/<Old ISF target-path>
          - <New ISF enterprise registry host>/<New ISF target-path>
          - <New ISF enterprise registry host:port>/<New ISF target-path>
          source: cp.icr.io/cp/spectrum/scale
        - mirrors:
          - <Old ISF enterprise registry host>/<Old ISF target-path>
          - <Old ISF enterprise registry host:port>/<Old ISF target-path>
          - <New ISF enterprise registry host>/<New ISF target-path>
          - <New ISF enterprise registry host:port>/<New ISF target-path>
          source: icr.io/cpopen
        #for IBM Spectrum Fusion operator 
        - mirrors:
          - <Old ISF enterprise registry host>/<Old ISF target-path>
          - <Old ISF enterprise registry host:port>/<Old ISF target-path>
          - <New ISF enterprise registry host>/<New ISF target-path>
          - <New ISF enterprise registry host:port>/<New ISF target-path>
          source: cp.icr.io/cp/isf-sds
        # for spp agent
        - mirrors:
          - <Old ISF enterprise registry host>/<Old ISF target-path>/sppc
          - <Old ISF enterprise registry host:port>/<Old ISF target-path>/sppc
          - <New ISF enterprise registry host>/<New ISF target-path>/sppc
          - <New ISF enterprise registry host:port>/<New ISF target-path>/sppc
          source: cp.icr.io/cp/sppc
        - mirrors:
          - <Old ISF enterprise registry host>/<Old ISF target-path>/sppc
          - <Old ISF enterprise registry host:port>/<Old ISF target-path>/sppc
          - <New ISF enterprise registry host>/<New ISF target-path>/sppc
          - <New ISF enterprise registry host:port>/<New ISF target-path>/sppc
          source: registry.redhat.io/amq7
        - mirrors:
          - <Old ISF enterprise registry host>/<Old ISF target-path>/sppc
          - <Old ISF enterprise registry host:port>/<Old ISF target-path>/sppc
          - <New ISF enterprise registry host>/<New ISF target-path>/sppc
          - <New ISF enterprise registry host:port>/<New ISF target-path>/sppc
          source: registry.redhat.io/oadp
        - mirrors: 
          - <New ISF enterprise registry host>/<New ISF target-path>/sppc 
          - <New ISF enterprise registry host:port>/<New ISF target-path>/sppc 
          source: registry.redhat.io/amq-streams

Procedure

  1. Log in to the OpenShift Container Platform management console as the cluster administrator.
  2. 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.6.0 or 2.6.1. Also, in the Subscription tab, ensure that the upgrade status displays Up to date.
  3. Upgrade IBM Storage Fusion services.
    For the steps to upgrade services, see Upgrading IBM Storage Fusion services.
  4. 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.
    Note: The Red Hat OpenShift Container Platform 4.13 is supported only from IBM Storage Fusion 2.6.1 release.

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
  • After you upgrade IBM Storage Fusion to 2.6, upgrade OpenShift Container Platform to 4.12 version. This OpenShift Container Platform upgrade restarts the CNSA operator and use the CNSA 5.1.7 version.