-
Bug
-
Resolution: Done-Errata
-
Critical
-
None
-
4.11.z
-
Critical
-
No
-
Rejected
-
False
-
This is a clone of issue OCPBUGS-3680. The following is the description of the original issue:
—
Description of problem:
OCP upgrade blocks because of cluster operator csi-snapshot-controller fails to start its deployment with a fatal message of read-only filesystem
Version-Release number of selected component (if applicable):
Red Hat OpenShift 4.11 rhacs-operator.v3.72.1
How reproducible:
At least once in user's cluster while upgrading
Steps to Reproduce:
1. Have a OCP 4.11 installed 2. Install ACS on top of the OCP cluster 3. Upgrade OCP to the next z-stream version
Actual results:
Upgrade gets blocked: waiting on csi-snapshot-controller
Expected results:
Upgrade should succeed
Additional info:
stackrox SCCs (stackrox-admission-control, stackrox-collector and stackrox-sensor) contain the `readOnlyRootFilesystem` set to `true`, if not explicitly defined/requested, other Pods might receive this SCC which will make the deployment to fail with a `read-only filesystem` message
- blocks
-
OCPBUGS-19511 4.12: Upgrade blocked: csi-snapshot-controller fails with read-only filesystem
- Closed
- clones
-
OCPBUGS-3680 4.15: Upgrade blocked: csi-snapshot-controller fails with read-only filesystem
- Closed
- is blocked by
-
OCPBUGS-18801 4.14 - Upgrade blocked: csi-snapshot-controller fails with read-only filesystem
- Closed
- is cloned by
-
OCPBUGS-19511 4.12: Upgrade blocked: csi-snapshot-controller fails with read-only filesystem
- Closed
- links to
-
RHBA-2023:5382 OpenShift Container Platform 4.13.z bug fix update