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

LVMS operator uninstall from console hangs forever deleting operands

XMLWordPrintable

    • Important
    • Yes
    • 2
    • OCPEDGE Sprint 253
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Previously, LVM Storage uninstallation was stuck waiting for the deletion of the LVMVolumeGroupNodeStatus operands. This fix corrects the behavior by ensuring all operands are deleted, allowing LVM Storage to be uninstalled without delay.
    • Bug Fix
    • Done

      This is an LVMS Bug Report:

      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:

       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

            [OCPBUGS-32753] LVMS operator uninstall from console hangs forever deleting operands

            Errata Tool added a comment -

            Since the problem described in this issue should be resolved in a recent advisory, it has been closed.

            For information on the advisory (LVMS 4.16 Bug Fix and Enhancement update), and where to find the updated files, follow the link below.

            If the solution does not work for you, open a new bug report.
            https://access.redhat.com/errata/RHBA-2024:4181

            Errata Tool added a comment - Since the problem described in this issue should be resolved in a recent advisory, it has been closed. For information on the advisory (LVMS 4.16 Bug Fix and Enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2024:4181

            Suleyman Akbas added a comment -

            I created another bug for the console team so this can be investigated on that side as well: https://issues.redhat.com/browse/OCPBUGS-33304 This bug should be fixed though by introducing a new removal logic in https://issues.redhat.com/browse/OCPBUGS-32954. 

            Suleyman Akbas added a comment - I created another bug for the console team so this can be investigated on that side as well: https://issues.redhat.com/browse/OCPBUGS-33304 This bug should be fixed though by introducing a new removal logic in https://issues.redhat.com/browse/OCPBUGS-32954 . 

            OpenShift Jira Bot added a comment -

            Hi sakbas@redhat.com,

            Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            OpenShift Jira Bot added a comment - Hi sakbas@redhat.com , Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.

            GitLab CEE Bot added a comment -

            CPaaS Service Account mentioned this issue in a merge request of ceph / lvms on branch lvms-4.16-rhel-9_upstream_d8b37f3e50c073bfe4e4ad38aaad91a1:

            Updated US source to: a0d9d60 Merge pull request #617 from suleymanakbas91/nodestatus-removal

            GitLab CEE Bot added a comment - CPaaS Service Account mentioned this issue in a merge request of ceph / lvms on branch lvms-4.16-rhel-9_ upstream _d8b37f3e50c073bfe4e4ad38aaad91a1 : Updated US source to: a0d9d60 Merge pull request #617 from suleymanakbas91/nodestatus-removal

            Suleyman Akbas added a comment -

            I couldn't find any behavior change in the console lately. The latest update to this logic was in 4.13. However, once the fix to OCPBUGS-32954 gets in, this bug will also be fixed.

            Suleyman Akbas added a comment - I couldn't find any behavior change in the console lately. The latest update to this logic was in 4.13. However, once the fix to OCPBUGS-32954 gets in, this bug will also be fixed.

              sakbas@redhat.com Suleyman Akbas
              mifiedle@redhat.com Mike Fiedler
              Rahul Deore Rahul Deore
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: