-
Bug
-
Resolution: Done
-
Critical
-
4.12
-
None
-
Critical
-
None
-
Storage Sprint 227, Storage Sprint 228, Storage Sprint 229
-
3
-
Approved
-
False
-
With CSISnapshot capability is disabled, all CSI driver operators are Degraded. For example AWS EBS CSI driver operator during installation:
18:12:16.895: Some cluster operators are not ready: storage (Degraded=True AWSEBSCSIDriverOperatorCR_AWSEBSDriverStaticResourcesController_SyncError: AWSEBSCSIDriverOperatorCRDegraded: AWSEBSDriverStaticResourcesControllerDegraded: "volumesnapshotclass.yaml" (string): the server could not find the requested resource AWSEBSCSIDriverOperatorCRDegraded: AWSEBSDriverStaticResourcesControllerDegraded: ) Ginkgo exit error 1: exit with code 1}
Version-Release number of selected component (if applicable):
4.12.nightly
The reason is that cluster-csi-snapshot-controller-operator does not create VolumeSnapshotClass CRD, which AWS EBS CSI driver operator expects to exist.
CSI driver operators must skip VolumeSnapshotClass creation if the CRD does not exist.
- blocks
-
OCPBUGS-3423 CSI driver operators are degraded without "CSISnapshot" capability
- Closed
- depends on
-
OCPBUGS-3978 AWS EBS CSI driver operator is degraded without "CSISnapshot" capability
- Closed
- is cloned by
-
OCPBUGS-3423 CSI driver operators are degraded without "CSISnapshot" capability
- Closed
- is related to
-
OCPBUGS-3425 [release-4.12] Azure Disk CSI Driver Operator gets degraded without "CSISnapshot" capability
- Closed
- links to