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 registryIf 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:
- Complete steps 1 to 8 of Mirroring Data Cataloging images procedure.
- 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 - 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:
- Complete steps 1 to 7 of Mirroring Data Foundation images deployed on OpenShift Container Platform version 4.12 topic.
- Before you upgrade IBM Storage Fusion, from the Services page of the IBM Storage Fusion user interface, disable Automatic updates for Data Foundation service.
- Go to , and check whether the Update approval is changed to Manually.
- Start the IBM Storage Fusion version upgrade.
- Update the image digest ID after you upgrade the IBM Storage Fusion as follows:
- 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.
- Ensure that the
data-foundation-serviceFusionServiceDefinitionCR is created.oc get fusionservicedefinitions.service.isf.ibm.com -n ibm-spectrum-fusion-ns data-foundation-service - Update the
imageDigestin theFusionServiceDefinitiondata-foundation-service.skopeo inspect docker://<enterprise registry host:port>/<target-path>/cpopen/isf-data-foundation-catalog:v4.12 | jq -r ".Digest" - 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-serviceExample 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
- Run the following command to get the catalog source image digest
ID.
- 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-secretusing 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 followinguser-install-secretsample 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-indexto 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
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
triggerUpgradeto 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.