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

[release-4.17] Wiping of local volume functionality failed on Multi-node cluster

XMLWordPrintable

    • None
    • 0
    • OCPEDGE Sprint 260
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • Release Note Not Required
    • In Progress

      This is a clone of issue OCPBUGS-42385. The following is the description of the original issue:
      —
      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:

      Test case OCP-71012:"Verify wiping of local volume", is failing on MNO cluster

Note: Same test-case passed on SNO cluster.Looks like forceWipe didn't remove children block devices.

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

       lvms 4.17.0-41

      Steps to Reproduce:

      Actual results:

       forceWipe didn't remove children block devices.    

      Expected results:

      All children devices should be wiped from all nodes

      Additional info:

       Failure reason:

reason: 'mandatory device path "/dev/nvme1n1" cannot be used, because it is NOT available as a new device for the volume group and NOT part of a valid and tagged existing volume group: /dev/nvme1n1 has children block devices and could not be considered'
          status: Failed

              rh-ee-jmoller Jakob Moeller (Inactive)
              openshift-crt-jira-prow OpenShift Prow Bot
              Rahul Deore Rahul Deore
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: