-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18, 4.19
-
Quality / Stability / Reliability
-
False
-
-
0
-
Low
-
None
-
None
-
None
-
OCPEDGE Sprint 270, OCPEDGE Sprint 271, OCPEDGE Sprint 275, OCPEDGE Sprint 276, OCPEDGE Sprint 279
-
5
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
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:
LVMCluster removal gets stuck if a node was removed from the cluster earlier. This is because of the remaining finalizer on the LVMVolumeGroup CR. The vg-manager controller responsible for removing this finalizer gets removed with the node before it has a chance to clean up the finalizer.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install LVMS on a multi-node cluster and create a LVMCluster CR. 2. Remove a node from the cluster. 3. Remove the LVMCluster, which gets stuck.
Actual results:
LVMCluster cannot be removed.
Expected results:
LVMCluster should be removed without any issues.
Additional info:
The workaround would be manual deletion of the remaining finalizers on the LVMVolumeGroup CR.
- is cloned by
-
OCPBUGS-58059 LVMCluster removal gets stuck if a node gets removed
-
- Closed
-
- is duplicated by
-
OCPBUGS-58068 LVMCluster removal gets stuck if a node gets removed
-
- Closed
-
- links to
- mentioned on
(1 mentioned on)