-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
4.14.z
Description of problem:
LSO as part of an ODF installation using logicalvolumeSet is using "sdX" device names instead of more stable ones even in case that better device names exists.
Version-Release number of selected component (if applicable):
Openshift 4.14
How reproducible:
Always on customer cluster
Steps to Reproduce:
1. 2. 3.
Actual results:
In the "localVolumeDiscoveryResults" object we can see that the volumes are being discovered with more stable names: - deviceID: /dev/disk/by-id/wwn-0x6000c29631bc5xxxxxxxxxxxxxxxxxx39 fstype: "" model: Virtual disk path: /dev/sdb property: Rotational serial: 6000c29631bc5xxxxxxxxxxxxxxxxx39 size: 1073741824000 status: state: NotAvailable type: disk vendor: VMware But this is what is being seen on /mnt/local-storage: total 0 drwxr-xr-x. 2 root root 109 Apr 15 12:56 . drwxr-xr-x. 3 root root 33 Nov 7 13:23 .. lrwxrwxrwx. 1 root root 54 Apr 15 12:55 sdb -> /dev/disk/by-id/wwn-0x6000c29631bc5xxxxxxxxxxxxxxxxx39 lrwxrwxrwx. 1 root root 54 Apr 15 12:56 wwn-0x6000c2951fad8xxxxxxxxxxxxxxxxx8e -> /dev/disk/by-id/wwn-0x6000c2951fad8xxxxxxxxxxxxxxxxx8e lrwxrwxrwx. 1 root root 54 Apr 15 12:54 wwn-0x6000c29631bc5xxxxxxxxxxxxxxxxx39 -> /dev/disk/by-id/wwn-0x6000c29631bc5xxxxxxxxxxxxxxxxx39
Expected results:
Direct use of the "wwn" or similar device names.
Additional info:
Even if we manually remove the "sdb" link it is being recreated and used. It is not yet confirmed but looks like if all the "wwn" links are created manually it seems to work without creating the "sdX" links.