Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-18397

Deletion of LVMCluster is stuck when VG no longer exists and doesn't remove lvmd conf entry for deviceClass

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 2
    • None
    • No
    • None
    • None
    • OCP VE Sprint 241, OCP VE Sprint 242, OCP VE Sprint 243, OCP VE Sprint 244
    • 4
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      LVMCluster gets stuck when the VG no longer exists as it currently errors out in https://github.com/openshift/lvm-operator/blob/main/pkg/vgmanager/vgmanager_controller.go#L285
This means that once the VG is gone, the deviceClass will never be removed and the PVs also never get removed.

      Version-Release number of selected component (if applicable):

      4.13-4.15

      How reproducible:

      100%

      Steps to Reproduce:

      1.Setup LVMCluster
2.Manually remove the VolumeGroup created from the deviceClass
3.Attempt to delete LVMCluster

      Actual results:

      LVMCluster deletion stuck and lvmd config never correctly updated

      Expected results:

      lvmd config gets removed deviceClass update and LVMCluster deletion proceeds normally

      Additional info:

      We should also split VG deletion and PV deletion just in case the VG no longer exists but the PV does.

              rh-ee-jmoller Jakob Moeller (Inactive)
              rh-ee-jmoller Jakob Moeller (Inactive)
              None
              None
              Rahul Deore Rahul Deore
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: