-
Epic
-
Resolution: Done-Errata
-
Major
-
openshift-4.13, openshift-4.14
-
LVMS Support for OpenShift without CSISnapshot Capability
-
Future Sustainability
-
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
Green
-
-
S
-
None
Epic Goal
In LVMS 4.14 and below, Snapshotting CRDs are expected to be present in the cluster at all times and startup will fail if they are not present. In OpenShift's install-config.yaml, one can disable Snapshotting via the CSISnapshot capability
This leads to us needing to support starting, running and testing LVMS without CSI Snapshotting support
Why is this important?
We want to support all capabilities in OpenShift as nicely as possible, and CSI Snapshots are not integral to the TopoLVM core functionality.
Acceptance Criteria
- QE Test Case with Cluster without CSISnapshot Capability must be created
- Be able to start and run LVMS without CSISnapshot Cabability
Dependencies (internal and external)
- Dependency on install-config.yaml set for the openshift-cluster to not contain the CSISnapshot Capability.
- https://issues.redhat.com//browse/OCPBUGS-18354 resolution contains a fix for the Watch Configuration that previously blocked startup for clusters without CSISnapshot Capability. Without this codepath being fixed, LVMS will not start properly
Done Checklist
- CI - CI is running, tests are automated and merged.
- Release Enablement <link to Feature Enablement Presentation>
- DEV - Upstream code and tests merged: https://github.com/openshift/lvm-operator/pull/405
- DEV - Upstream documentation merged: N/A
- DEV - Downstream build attached to advisory: <link to errata>
- QE - Test plans in Polarion: <link or reference to Polarion>
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: <link to meaningful PR>
- is related to
-
USHIFT-1626 make CSI snapshotting optional
-
- Closed
-
- links to
-
RHBA-2024:126443 LVMS 4.15 Bug Fix and Enhancement update