Vertical Pod Autoscaler Operator inadvertently upgraded to v4.18 version on OCP4.12-4.17 clusters
Issue
Between 2026-02-03 21:16 UTC and 2026-02-04 05:18 UTC, a catalog release error caused OCP 4.18 operator content to be pushed to OCP 4.12–4.17 clusters.
Clusters with subscriptions set to Automatic approval may have inadvertently upgraded the Vertical Pod Autoscaler Operator to a version intended for OCP 4.18.
This article specifically addresses how to:
- Verify if your GCP Filestore CSI Driver was affected by this specific window of misconfiguration.
- Roll back or recover the driver to the version appropriate for your OCP release.
Resolution
Downgrade the Vertical Pod Autoscaler Operator
If the 4.18 version of the Vertical Pod Autoscaler Operator has been installed, it can be downgraded by removing it and reinstalling it. During the process the Vertical Pod Autoscaler should continue to function with only a short window of unavailability when the new subscription is created and the correct version pods replace the wrong version pods.
Follow these steps to remove the incorrect version and trigger a fresh installation of the supported version.
-
Find the incorrect CSV
$ oc get csv -A | grep "Vertical Pod Autoscaler Operator" openshift-vertical-pod-autoscaler vertical-pod-autoscaler.v4.18.0-202601302238 Vertical Pod Autoscaler Operator 4.18.0-202601302238 verticalpodautoscaler.4.12.0-202602021306 SucceededMake note of the values from the first two columns, which are the CSV's namespace and the CSV name
-
Find the subscription. If different from the command below, replace the CSV name discovered in step 1
$ oc get subscription -A -o custom-columns=NAMESPACES:.metadata.namespace,NAME:.metadata.name,CSV:.status.currentCSV | grep vertical-pod-autoscaler.v4.18.0-202601302238 openshift-vertical-pod-autoscaler vertical-pod-autoscaler vertical-pod-autoscaler.v4.18.0-202601302238Make note of the values from the first two columns, which are the subscription's namespace and the subscription name
-
Delete the incorrect CSV
Replace with CSV namespace and CSV name identified in step above, if different from the command below.
$ oc delete csv -n openshift-vertical-pod-autoscaler vertical-pod-autoscaler.v4.18.0-202601302238 clusterserviceversion.operators.coreos.com "vertical-pod-autoscaler.v4.18.0-202601302238" deleted -
Delete the existing subscription:
Replace with subscription namespace and subscription name identified in step 2, if different from the command below.
$ oc delete subscription -n openshift-vertical-pod-autoscaler vertical-pod-autoscaler subscription.operators.coreos.com "vertical-pod-autoscaler" deleted -
Reinstall the Vertical Pod Autoscaler Operator using the OperatorHub section of the OpenShift console.
-
Verification
Verify that the new CSV version matches your OCP version. In the following example from a 4.12 cluster, the CSV versions are listed as 4.12.0-202602021306 which is an appropriate version for an OpenShift 4.12 cluster.
$ oc get csv -A |grep vertical-pod-autoscaler openshift-vertical-pod-autoscaler verticalpodautoscaler.4.12.0-202602021306 VerticalPodAutoscaler 4.12.0-202602021306 Succeeded
Diagnostic Steps
-
Check to see if the incorrect CSV is installed
$ oc get csv -A | grep "Vertical Pod Autoscaler Operator" openshift-vertical-pod-autoscaler vertical-pod-autoscaler.v4.18.0-202601302238 Vertical Pod Autoscaler Operator 4.18.0-202601302238 verticalpodautoscaler.4.12.0-202602021306 Succeeded
In this example from an OpenShift version 4.12 cluster, the CSV version is expected to be version 4.12.0-, but instead it is 4.18.0-. In this case, the above remediation steps should be followed to downgrade by removing and reinstalling VPA.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.