IBM Fusion HCI 2.11.0: Dell GPU hotfix

It includes configuration changes that enable the IBM Fusion user interface to detect and display the new adapter hardware. As a result, the GPU nodes inventory is fully visible, and runtime issues that cause the user interface to fail are resolved.

Note: Apply this hotfix after stage 2 is completed on the rack when the cluster is up and running on the rack.

Requirements for offline environments:

1. Run the following commands to mirror the compute operator and user interface images to your offline registry:
   
   skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:4a420e2e9930ace93a16e636f090f2b5332beb87c8ede816aba104de529e8c32 docker://$TARGET_PATH/cp/fusion-hci/isf-compute-operator@sha256:4a420e2e9930ace93a16e636f090f2b5332beb87c8ede816aba104de529e8c32

skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/fusion-hci/fusion-ui@sha256@sha256:a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33 docker://$TARGET_PATH/cp/fusion-hci/fusion-ui@sha256:a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33
   
   Replace the $TARGET_PATH with the path to your target offline registry.
   
   For example:
   
   If your TARGET_PATH is: docker-na-public.artifactory.swg-devops.com/hyc-abell-devops-team-dev-offline-docker-local/hci-auto-ga-211
   
   Then the commands would be:
   
   skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:4a420e2e9930ace93a16e636f090f2b5332beb87c8ede816aba104de529e8c32 docker://docker-na-public.artifactory.swg-devops.com/hyc-abell-devops-team-dev-offline-docker-local/hci-auto-ga-211/cp/fusion-hci/isf-compute-operator@sha256:4a420e2e9930ace93a16e636f090f2b5332beb87c8ede816aba104de529e8c32

skopeo copy --insecure-policy --preserve-digests --all docker://cp.icr.io/cp/isf/fusion-ui@sha256:a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33 docker://docker-na-public.artifactory.swg-devops.com/hyc-abell-devops-team-dev-offline-docker-local/hci-auto-ga-211/fusion-ui@sha256:a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33
    
2. Follow the resolution steps to apply the hotfix.
    

Requirements for online environments:

• Use the following images directly to apply the hotfix:
  • Compute operator image - cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:4a420e2e9930ace93a16e636f090f2b5332beb87c8ede816aba104de529e8c32
  • User interface operator image - cp.icr.io/cp/fusion-hci/fusion-ui@sha256@sha256:a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33

Resolution:

1. Update the IBM Storage Fusion operator as follows:
   1. Log in to the OpenShift Container Platform web console.
   2. Go to Operators  > Installed Operators.
   3. In the Project drop-down, select the ibm-spectrum-fusion-ns namespace.
   4. Click the IBM Storage Fusion installed operator.
   5. Click the YAML tab to open the YAML editor screen.
   6. In the editor, search for the string isf-compute-operator@sha256.
   7. Under the label control-plane: isf-compute-operator, update the image in the manager container field with the new compute operator image.
      
      For example:
      /manager
image: cp.icr.io/cp/fusion-hci/isf-compute-operator@sha256:4a420e2e9930ace93a16e636f090f2b5332beb87c8ede816aba104de529e8c32
      
      Note: If the setup is offline, replace the value of image with the corresponding compute operator offline image.
       

   8. Click Save.

2. Verify the isf-compute-operator pod as follows:
   1. Run oc get po to list the pods.
   2. Run oc describe po <isf-compute-operator-pod-name> to inspect the image used in the manager container.
       
3. Update the management user interface configmap as follows:
   1. Go to Workloads > ConfigMaps.
   2. In the Project drop-down, select the ibm-spectrum-fusion-ns namespace.
   3. Search for the configmap named cr-version-cm and open it.
   4. Click the YAML tab to edit the configmap.
   5. Search for the key isf-management-ui_image_path and update its value to:
      
      cp.icr.io/cp/fusion-hci/fusion-ui@sha256
      
      Note: If the setup is offline, replace the value of isf-management-ui_image_path with the corresponding image path. For example, $TARGET_PATH/cp/fusion-hci/fusion-ui@sha256.
       
   6. Search for the key isf-management-ui_version and update its value to:
      
      a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33
   7. Confirm the ConfigMap looks like the following and click Save:
      
      {
        "isf-management-ui_image_path": "cp.icr.io/cp/fusion-hci/fusion-ui@sha256",
        "isf-management-ui_version": "a8572133016d8a241f2dee5bca193fed5e26a809e76bd03f23996cb160e6bf33"
      }
      
      Note: The isf-management-ui_image_path would be different for offline setup.
   8. Acknowledge the warning that the configmap is managed by another resource.
       
4. Redeploy the management user interface as follows:
   1. Go to Workloads > Deployments.
   2. Search for the isf-ui-dep deployment and delete it.
   3. Confirm the deletion and select the Delete dependent resources check box.
   4. The isf-ui-dep deployment automatically redeploy using the updated image from the cr-version-cm.