-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-61988. The following is the description of the original issue:
—
Description of problem:
Under certain circumstances, storage hardware implementation can cause a non-unique value to be populated under '/dev/disk/by-id' for a device. When this happens, LocalVolumeSet device discovery cannot consistently select the correct device reference. This can result in LSO symlinks pointing to incorrect devices after a reboot. If a LocalVolumeSet allowed a device filter to be specified then problematic devices could be ignored.
Version-Release number of selected component (if applicable):
4.18
How reproducible:
Consistently
Steps to Reproduce:
Actual results:
Non-unique device references in '/dev/disk/by-id' cause the LSO symlinks to sometimes be inconsistent, where the wrong backend disk gets referenced.
Expected results:
Problematic devices could be ignored by an LSO LocalVolumeSet so device references are consistent.
Additional info:
- blocks
-
OCPBUGS-62764 LocalVolumeSet cannot filter out non-unique '/dev/disk/by-id' references
-
- Verified
-
- clones
-
OCPBUGS-61988 LocalVolumeSet cannot filter out non-unique '/dev/disk/by-id' references
-
- Verified
-
- is blocked by
-
OCPBUGS-61988 LocalVolumeSet cannot filter out non-unique '/dev/disk/by-id' references
-
- Verified
-
- is cloned by
-
OCPBUGS-62764 LocalVolumeSet cannot filter out non-unique '/dev/disk/by-id' references
-
- Verified
-
- links to