Closed nin0-0 closed 4 months ago
We've noticed the automatic upgrade was enabled for the operator and it's in broken state.
Name: certified-operators
Namespace: openshift-marketplace
Identifier: hpe-csi-operator.v2.4.1
Path: registry.connect.redhat.com/hpestorage/csi-driver-operator-bundle@sha256:b5f87d6a9c7ec3a4d53204e86d0fa57d10d4aba2eeb1882f0a1b1caa19c7d9fd
Properties: {"properties":[{"type":"olm.gvk","value":{"group":"storage.hpe.com","kind":"HPECSIDriver","version":"v1"}},{"type":"olm.package","value":{"packageName":"hpe-csi-operator","version":"2.4.1"}}]}
Replaces: hpe-csi-operator.v2.4.0
Catalog Sources:
Conditions:
Last Transition Time: 2024-03-04T17:51:58Z
Last Update Time: 2024-03-04T17:51:58Z
Message: error validating existing CRs against new CRD's schema for "hpecsidrivers.storage.hpe.com": error validating custom resource against new schema for HPECSIDriver hpe-csi-driver/csi-driver: [].spec.disable.alletraStorageMP: Required value
can you advise what to do to resolve? 2.4.0 is in replacing state and 2.4.1 is in Pending
only found this: https://github.com/hpe-storage/csi-driver/blob/master/release-notes/v2.4.1.md not in releases even
should we edit the old CRD to include the disable.alletraStorageMP ?
or follow this https://scod.hpedev.io/partners/redhat_openshift/index.html#upgrading
The operator is currently broken. We're working with Red Hat to have it resolved.
The 2.4.0 release has been restored.
how do we get out of the broken state though?
OCP 4.12 hpe csi driver 2.4.0
We're trying to deploy IBM TNCP (proviso) and only some pods of the deployment are failing with:
In the related hpe-csi-driver pod we see this:
Please help us to debug this and/or point the relevant issue.
thanks