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

Removing LVMCluster CR does not trigger the removal of LVMVolumeGroupNodeStatus CRs

XMLWordPrintable

    • Low
    • No
    • 2
    • OCPEDGE Sprint 253
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Hide
      Previously, some LVMVolumeGroupNodeStatus operands were not deleted on the cluster during the deletion of the LVMCluster custom resource (CR). With this release, deleting the LVMCluster CR triggers the deletion of all the LVMVolumeGroupNodeStatus operands.
      Show
      Previously, some LVMVolumeGroupNodeStatus operands were not deleted on the cluster during the deletion of the LVMCluster custom resource (CR). With this release, deleting the LVMCluster CR triggers the deletion of all the LVMVolumeGroupNodeStatus operands.
    • Bug Fix
    • Done

      Please create & attach a must-gather as indicated by this Guide to collect LVMS relevant data from the Cluster (linked to the latest version, use older versions of the documentation for older OCP releases as applicable

      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:

      Removing LVMCluster CR does not trigger the removal of LVMVolumeGroupNodeStatus CRs. This can be mitigated easily by removing these resources manually, but this should ideally be done by lvm-operator.

              sakbas@redhat.com Suleyman Akbas
              sakbas@redhat.com Suleyman Akbas
              Rahul Deore Rahul Deore
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: