-
Bug
-
Resolution: Done-Errata
-
Major
-
4.15.z, 4.16.0
-
Important
-
Yes
-
2
-
OCPEDGE Sprint 253
-
1
-
Rejected
-
False
-
-
Previously, LVM Storage uninstallation was stuck waiting for the deletion of the LVMVolumeGroupNodeStatus operands. This fix corrects the behavior by ensuring all operands are deleted, allowing LVM Storage to be uninstalled without delay.
-
Bug Fix
-
Done
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:
After installing LVMS 4.16.0-42 and creating an LVMCluster, attempts to uninstall the operator from the console hang at "Cleaning up operand instances. Operands remaining: 1 of 3." I've let it sit for hours and it does not complete.
Version-Release number of selected component (if applicable):
4.16.0-42
Steps to Reproduce:
1. Install LVMS 4.16.0-42 on an AWS SNO with an extra volume for lvm to use 2. Create an LVMCluster (no pv/pvc) 3. From the console uninstall the operator (select "Delete all operand instances" checkbox)
Actual results:
Hangs at "Cleaning up operand instances. Operands remaining: 1 of 3." The LVMCluster and StorageClass are gone. The vg-manager pod is gone, but the operator pod is still there. The CRDs are still there.
Expected results:
Clean uninstall
Additional info:
Blocks verification of https://issues.redhat.com/browse/OCPBUGS-29225
- depends on
-
OCPBUGS-32954 Removing LVMCluster CR does not trigger the removal of LVMVolumeGroupNodeStatus CRs
- Closed
- is triggering
-
OCPBUGS-33304 Console does not remove one of the LVMS CRs when operand removal is opted
- Closed
- links to
-
RHBA-2024:129552 LVMS 4.16 Bug Fix and Enhancement update
- mentioned on