-
Bug
-
Resolution: Unresolved
-
Major
-
4.15.z, 4.16.0
-
Important
-
Yes
-
2
-
OCPEDGE Sprint 253
-
1
-
Rejected
-
False
-
-
Before this fix, the removal of LVMS was stuck waiting for the deletion of LVMVolumeGroupNodeStatus CRs. After this fix, all the operands are timely removed so no hanging occurs.
-
Bug Fix
-
In Progress
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
-
-
- Verified
-
- is triggering
-
-
- New
-
- mentioned on
