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

[release-4.17] LVM fails to reconcile LVMVolumeGroupNodeStatus after node removal

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • None
    • None
    • None
    • OCPEDGE Sprint 270, OCPEDGE Sprint 271
    • 2
    • Done
    • Bug Fix
    • Hide
      Previously, the node controller previously did not remove the finalizer from LVMVolumeGroupNodeStatus objects during node deletion, resulting in orphaned resources. With this fix, the controller now properly removes the finalizer, allowing the objects to be cleaned up as expected.
      Show
      Previously, the node controller previously did not remove the finalizer from LVMVolumeGroupNodeStatus objects during node deletion, resulting in orphaned resources. With this fix, the controller now properly removes the finalizer, allowing the objects to be cleaned up as expected.
    • None
    • None
    • None
    • None

      This is a clone of issue OCPBUGS-54154. The following is the description of the original issue:
      —

      Description of problem:

      When removing a node the LVMVolumeGroupNodeStatus is not reconciled leaving LVMVolumeGroupNodeStatus, finalizers in LVMVolumeGroup and status information (in LVMCluster) on the cluster.

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

      lvms-operator.v4.17

      Steps to Reproduce:

      machine/node is deprovisioned, LVMVolumeGroupNodeStatus remains

      Actual results:

      LVMVolumeGroupNodeStatus remains

      Expected results:

      LVMVolumeGroupNodeStatus and other dependant objects should be reconciled

      Additional info:

              sakbas@redhat.com Suleyman Akbas
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Minal Pradeep Makwana Minal Pradeep Makwana
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: