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

mpath device type missing in LocalVolumeDiscovery CR

    XMLWordPrintable

Details

    • Important
    • No
    • Storage Sprint 235, Storage Sprint 236, Storage Sprint 237, Storage Sprint 239, Storage Sprint 240
    • 5
    • Rejected
    • False
    • Hide

      None

      Show
      None
    • N/A
    • Release Note Not Required

    Description

      Description of problem:

      When ODF StorageSystem CR gets created through the Wizard, the LocalVolumeDiscovery doesn't bring/show devices with mpath type

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

      OCP 4.11.31

      How reproducible:

      All the time

      Steps to Reproduce:

      1. Get OCP 4.11 running with the LSO and ODF operators
2. Configure and present mpath devices to nodes used for ODF
3. Use the ODF wizard to create a StorageSystem object
4. Inspect the LocalVolumeDiscovery results.

      Actual results:

      There are no devices of mpath type shown by the ODF wizard / LocalVolumeDiscovery CR

      Expected results:

      LocalVolumeDiscovery should discover mpath device type

      Additional info:

      LocalVolumeSet already works with mpath if you manually define them in .spec or  LocalVolume pointing to mpath devicePaths

      Attachments

        Issue Links

          blocks

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-13285 mpath device type missing in LocalVolumeDiscovery CR

          • Undefined - Priority not specified.
          • Closed
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. OCPBUGS-13285 mpath device type missing in LocalVolumeDiscovery CR

          • Undefined - Priority not specified.
          • Closed
          is documented by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. STOR-1430 [doc] mpath device type support for LSO

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • To Do
          links to

          GitHub openshift/console#12723: OCPBUGS-10884: add multipath device type to LocalVolumeSet

          GitHub openshift/console#13022: OCPBUGS-10884: propagate mpath device type to request data

          GitHub openshift/local-storage-operator#394: OCPBUGS-10884: add multipath support for volume discovery

          Web Link RHEA-2023:5005 rpm

          Activity

            People

              rbednar@redhat.com Roman Bednar
              rhn-support-jcoscia Javier Coscia
              Penghao Wang Penghao Wang
              Lisa Pettyjohn Lisa Pettyjohn
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: