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

LVMS forced cleanup procedure does not work

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • All
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This is an LVMS Bug Report:

      Description of problem:

      I am following the forced cleanup procedure documented here:
      https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html/storage/persistent-storage-using-local-storage#performing-a-forced-cleanup_logical-volume-manager-storage

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

       4.20

      Steps to Reproduce:

      Step  3 asks me to delete the lvmvolumegroup objects by removing the finaliser:
% oc delete lvmvolumegroup/local-ssd 
lvmvolumegroup.lvm.topolvm.io "local-ssd" deleted
% oc patch lvmvolumegroup local-ssd -p '{"metadata":{"finalizers":[]}}' --type=merge                     
lvmvolumegroup.lvm.topolvm.io/local-ssd patched (no change)
 % oc get lvmvolumegroup
NAME        AGE
local-ssd   30s

       

      Actual results:

      The lvmvolumegroup is instantly re-created

      Expected results:

      lvmvolumegroup shoud be deleted

      Additional info:

      I think the sequence is wrong. Probably the LVMCluster object needs to be deleted first, but it is per the doc only deleted in step 5

              bzamalut@redhat.com Bulat Zamalutdinov
              dfroehli42rh Daniel Fröhlich
              None
              None
              Minal Pradeep Makwana Minal Pradeep Makwana
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: