Created attachment 1996211 [details] Storagesystem creation Description of problem (please be detailed as possible and provide log snippets): Storagesystem creation from webui using local storage devices is not detecting multipath devices by default. Rescanning of devices is not happening after Mpath device is selected from the dropdown. Please see attached screenshot. As an alternative I am able to create localvolumeset manually using the below yaml file which then detect multipath device properly. After creating localvolumeset manually, the deployment of odf works fine using the respective storageclass. apiVersion: local.storage.openshift.io/v1alpha1 kind: LocalVolumeSet metadata: name: localblock namespace: openshift-local-storage spec: deviceInclusionSpec: deviceTypes: - disk - part - mpath minSize: 1Gi nodeSelector: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - worker-0.ocsm1301001.lnxero1.boe - worker-1.ocsm1301001.lnxero1.boe - worker-2.ocsm1301001.lnxero1.boe storageClassName: localblock tolerations: - effect: NoSchedule key: node.ocs.openshift.io/storage operator: Equal value: 'true' volumeMode: Block Version of all relevant components (if applicable): Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install OCP 4.14 followed by localstorage and Openshift Data foundation operators deployment. 2. Attach multipath devices on the storage nodes. 3. Create storagesystem from web console. Actual results: multipath devices not getting detected. Expected results: multipath devices get detected and listed. Additional info:
This is a duplicate bug, please use latest ODF 4.14 for your testing, refer: https://bugzilla.redhat.com/show_bug.cgi?id=2182351#c25 Also make sure disks are in "Available" state, else UI will not detect them.
Also, what was the exact ODF version used for this BZ ??
This was tested with ODF version : 4.14.0-152.. I see that the referred BZ is fixed with a later version.. i will try it out.
can u please check the state of the disks ? is type of the disks "mpath" and disks are in "Available" state ?? (refer: https://bugzilla.redhat.com/show_bug.cgi?id=2182351#c2 for more details).
this bug was fixed in ODF 4.14 (https://bugzilla.redhat.com/show_bug.cgi?id=2182351) and doc text is already provided as part of that. Removing RDT flag for this BZ.
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: Red Hat OpenShift Data Foundation 4.15.0 security, enhancement, & bug fix 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-2024:1383