Bug 2089387

Summary: LSO not taking mpath. ignoring device
Product: OpenShift Container Platform Reporter: Javier Coscia <jcoscia>
Component: StorageAssignee: Hemant Kumar <hekumar>
Storage sub component: Local Storage Operator QA Contact: Penghao Wang <pewang>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: etamir, gcharot, hekumar, jdobson, jsafrane, kpelc, ktordeur, openshift-bugs-escalate, srengan, wduan
Version: 4.9   
Target Milestone: ---   
Target Release: 4.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-08-10 11:13:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Javier Coscia 2022-05-23 14:38:07 UTC
Description of problem:

- When installing ODF 4.9 with internal local storage using LSO, the creation of the StorageSystem cannot move forward because there are no available devices for the ODF cluster.

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

- OpenShift 4.9.29
- ODF 4.9.6
- LSO local-storage-operator.4.9.0-202204211825

How reproducible:

- All the time on user's environment

Steps to Reproduce:
1. Present a device with multiple paths to the storage nodes
2. Device gets visible through multipath as mpath device (multipath -ll)
3. Create a StorageSystem using local storage devices
4. In step 2, "create logical volume set", the filter gets zero matches because `mpath` device is listed as invalid

Actual results:

- Cannot install ODF with local storage using LSO

Expected results:

- Be able to complete the installation


Master Log:

Node Log (of failed PODs):

PV Dump:

PVC Dump:

StorageClass Dump (if StorageClass used by PV/PVC):

Additional info:

Comment 6 Jan Safranek 2022-05-24 14:15:25 UTC
Historically, LSO supported all local block devices, regardless of the actual backend and transport protocol. We would like to continue with that and fix multipath, it's up to ODF if they want to consume such devices for Ceph. It's up to the node admin to create such block devices and keep them working using standard RHEL / RHOCS tools and their support.

Using EMC CSI driver, as suggested by Greg above would be probably a better option.

Comment 21 errata-xmlrpc 2022-08-10 11:13:36 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security 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/RHSA-2022:5069