This is a clone of issue OCPBUGS-30830. The following is the description of the original issue:
—
This is an LVMS Bug Report:
Please make sure that you describe your storage configuration in detail. List all devices that you plan to work with for LVMS as well as any relevant machine configuration data to make it easier for an engineer to help out.
Description of problem:
[LVMS] After OCP multi-node upgrade, existing LVMClsuter CR stuck in 'Progressing' state
Version-Release number of selected component (if applicable):
LVMS 4.14.3
Steps to Reproduce:
1. Install LVMS operator 4.14.3 on OCP multi-node cluster successfully 2. Upgrade OCP 4.14 to 4.15 successfully 3. Check LVMCluster CR status on upgraded OCP cluster 4. LVMCluster CR stuck in 'Progressing' state
Actual results:
LVMCluster CR stuck in 'Progressing' state
Expected results:
LVMCluster CR goes into 'Running' state
Additional info:
LVMS resource pods are observed to be in 'Running' state, only lvmCluster CR is in 'Progressing' state.
- clones
-
OCPBUGS-30830 [LVMS] After OCP multi-node upgrade LVMCluster CR stuck in 'Progressing' state
- ON_QA
- is blocked by
-
OCPBUGS-30830 [LVMS] After OCP multi-node upgrade LVMCluster CR stuck in 'Progressing' state
- ON_QA
- links to
-
RHBA-2024:131911 LVMS 4.15.4 Bug Fix Update