Upgrading InfoScale (InfoScale/Software only upgrade)

Last published : Jul 06, 2026
Note: Refer to this section if you intend to upgrade InfoScale to 9.2.0 only, and perform the OpenShift platform upgrade separately.
Patch InfoScale cluster version to 9.2.0
With this step, you are triggering the software upgrade for the InfoScale cluster.
oc patch infoscalecluster <cluster-name>  -n <namespace>
--type=merge  -p '{"spec":{"version":"9.2.0"}}'
infoscalecluster.infoscale.veritas.com/<namespace> patched

Wait for cluster to be in running state  and rollout to be complete
\# oc get po -n infoscale-vtas
NAME                                           READY  STATUS       RESTARTS     AGE
infoscale-csi-controller-569fb9fc4-k6ddn       5/5    Running      1 (51s ago)  57s
infoscale-csi-node-c85tf                       2/2    Running      0            27s
infoscale-csi-node-cpwrt                       2/2    Terminating  0            3d5h
infoscale-csi-node-gsx5d                       2/2    Running      0            3d5h
infoscale-csi-node-xfgjn                       2/2    Running      0            3d5h
infoscale-fencing-controller-5b86c59dfd-f7ptw  1/1    Running      0            3d5h
infoscale-fencing-enabler-6mx7d                1/1    Running      0            3d5h
infoscale-fencing-enabler-j8zgw                1/1    Running      0            3d5h
infoscale-fencing-enabler-qrxtw                1/1    Running      0            3d5h
infoscale-fencing-enabler-tjcbk                1/1    Running      0            3d5h
infoscale-licensing-operator-7bb6cb7d48-5hz5b  1/1    Running      0            3d14h
infoscale-sds-1230-1eb7816cdb4bd7f3-drhlq      1/1    Running      0            3d5h
infoscale-sds-1230-1eb7816cdb4bd7f3-fzdzl      1/1    Running      0            3d5h
infoscale-sds-1230-1eb7816cdb4bd7f3-gf62d      1/1    Running      0            3d5h
infoscale-sds-1230-1eb7816cdb4bd7f3-hq6b9      1/1    Running      0            3d5h
infoscale-sds-operator-66c66c6ccf-wfzv4        1/1    Running      0            2m49s
infoscale-toolset-1230-6bc76b6b96-64flx        1/1    Running      0            3d5h
infoscale-toolset-1230-6bc76b6b96-87jrp        1/1    Running      0            3d5h
infoscale-toolset-1230-6bc76b6b96-mggxs        1/1    Running      0            3d5h
infoscale-toolset-1230-6d9f474779-nwb26        0/1    Running      0            32s
---
\# oc get infoscaleclusters -A
NAMESPACE        NAME                   VERSION   CLUSTERID   STATE
infoscale-vtas   infoscalecluster-dev   9.1.3   1230        Upgrading

DISKGROUPS          STATUS    AGE
vrts_kube_dg-1230   Healthy   3d5h
VM migration retries During a software upgrade in environments with OCP-V workloads, the system manages VM migrations to facilitate node rollouts. If a VM migration fails due to a timeout, the following retry logic is applied:
  • The system automatically retries failed migrations.
  • A maximum of five total attempts is recommended (the initial attempt plus four retries).
  • Setting the retry count beyond five is not recommended, as it can interfere with the OCPV controller's garbage collection process. -If the maximum retry count is exhausted, the upgrade process pauses. The user must then perform the migration manually or delete the failed migration resources to allow the upgrade workflow to resume automatically.
Upgrade sanity monitoring
The upgrade sanity monitoring process serves as a protective guard during software upgrades to prevent issues related to kernel module removal. This process occurs when rolling out the Storage Delivery System (SDS) pods without rebooting the nodes.
  • Before an older SDS pod is deleted, the system checks for any open volume references.
  • The system creates intermediate "upgrade sanity" pods to perform these checks.
  • In successful cases where no open volume references are detected, these pods are automatically deleted, and the upgrade proceeds without being visible to the user.
  • If an open volume reference is found, the upgrade is completely paused to avoid improper termination of services (such as vxvm stop).
  • When a pause occurs, the user must identify the pod holding the volume and either delete or move that pod to allow the upgrade to resume automatically.
Wait for completion of software upgrade
At this stage, you will see the changes roll out first for CSI, fencing, and the Toolset, followed by the SDS. The cluster status will switch between "Degraded" and "Running" because nodes leave the cluster one at a time to upgrade and then rejoin. The time this takes will depend on the workload running on your system.
infoscale-vtas   infoscalecluster-dev   9.1.3   1230
Upgrading   vrts_kube_dg-1230   Degraded   38m

infoscale-vtas   infoscalecluster-dev   9.1.3   1230
Upgrading   vrts_kube_dg-1230   Healthy    39m

infoscale-vtas   infoscalecluster-dev   9.2.0     1230
Running     vrts_kube_dg-1230   Healthy    39m