gcp-filestore operator inadvertently upgraded to v4.18 version on OCP4.14-4.17 clusters

Solution Verified - Updated

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 GCP Filestore CSI Driver Operator to a version intended for OCP 4.18.

This article specifically addresses how to:

  1. Verify if your GCP Filestore CSI Driver was affected by this specific window of misconfiguration.
  2. Roll back or recover the driver to the version appropriate for your OCP release.

Resolution

Downgrade the GCP Filestore CSI Driver Operator

Follow these steps to remove the incorrect version and trigger a fresh installation of the supported version.

1. Find the incorrect CSV

~> oc -n openshift-cluster-csi-drivers get csv
NAME                                                     DISPLAY                             VERSION               REPLACES                                                 PHASE
gcp-filestore-csi-driver-operator.v4.18.0-202601302238   GCP Filestore CSI Driver Operator   4.18.0-202601302238   gcp-filestore-csi-driver-operator.v4.14.0-202601210114   Succeeded

2. Delete the incorrect CSV

Replace <CSV_NAME> with name we identified in step above.

~> oc -n openshift-cluster-csi-drivers delete csv CSV_NAME

From above example it would be:

~> oc -n openshift-cluster-csi-drivers delete csv gcp-filestore-csi-driver-operator.v4.18.0-202601302238

3. Remove existing subscription:

First find out existing subscription:

~> oc -n openshift-cluster-csi-drivers get subscriptions.operators.coreos.com

And then delete it:

~> oc -n openshift-cluster-csi-drivers delete subscriptions.operators.coreos.com gcp-filestore-csi-driver-operator

4. Recreate subscription with version of operator that matches your Openshift cluster's version:

oc apply -f - <<EOF
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
 name: gcp-filestore-csi-driver-operator
 namespace: openshift-cluster-csi-drivers
spec:
 channel: stable
 installPlanApproval: Manual
 name: gcp-filestore-csi-driver-operator
 source: redhat-operators
 sourceNamespace: openshift-marketplace
EOF

Example output:

subscription.operators.coreos.com/gcp-filestore-csi-driver-operator created

5. Verification

Verify that subscription matches your OCP version.

~> oc -n openshift-cluster-csi-drivers get csv
NAME                                                     DISPLAY                             VERSION               REPLACES   PHASE
gcp-filestore-csi-driver-operator.v4.14.0-202601210114   GCP Filestore CSI Driver Operator   4.14.0-202601210114              Succeeded

Diagnostic Steps

You may be affected by this issue if you are running Openshift version <v4.18 and have gcp-filestore-operator running on v4.18:

~> oc -n openshift-cluster-csi-drivers get csv
NAME                                                     DISPLAY                             VERSION               REPLACES                                                 PHASE
gcp-filestore-csi-driver-operator.v4.18.0-202601302238   GCP Filestore CSI Driver Operator   4.18.0-202601302238   gcp-filestore-csi-driver-operator.v4.14.0-202601210114   Succeeded

In above example, you can see that CSV version is 4.18 and hence operator version also must be 4.18

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.