-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
rhel-9.4.z
-
None
-
Important
-
ce939e69e89d8359d19eecb9c2243185e1b2783a
-
rhel-storage-management
-
None
-
False
-
False
-
-
None
-
None
-
None
-
None
-
Unspecified
-
Unspecified
-
Unspecified
-
-
Linux
-
None
Description of problem:
OpenShift 4.18 (RHEL 9.4) has a udev rule that is causing problems for some major customers (see OCPBUGS-61988 for details):
/usr/lib/udev/rules.d/63-scsi-sg3_symlink.rules
38 ENV{SCSI_IDENT_LUN_VENDOR}=="?*", ENV{DEVTYPE}=="disk", SYMLINK+="disk/by-id/scsi-0$env{SCSI_VENDOR}_$env{SCSI_MODEL}_$env{SCSI_IDENT_LUN_VENDOR}"
SCSI_IDENT_LUN_VENDOR is not unique for the vendor they're using, which makes /dev/disk/by-id/scsi-0NVME_MO006400KXPTU_1c5c1590 non-deterministic on reboot.
The node is running sg3_utils-1.47-9.el9.x86_64, and the problematic udev rule was disabled by default upstream starting in sg3_utils 1.48:
https://github.com/hreinecke/sg3_utils/commit/ce939e69e89d8359d19eecb9c2243185e1b2783a#diff-8c40f74650212ce8122a1e96f7ae3c62a212342e14a91dcd3be828f058a1fe3fL35
That fix is in centos 10 now, but not earlier versions. We're requesting a backport to RHEL 9.4.z.
Version-Release number of selected component (if applicable):
RHEL 9.4
How reproducible:
Consistently on this hardware
Steps to Reproduce:
Actual results:
Non-unique device references in '/dev/disk/by-id' cause the symlinks to sometimes be inconsistent, where the wrong backend disk gets referenced.
Expected results:
Symlinks under /dev/disk/by-id are always stable
Additional info:
- blocks
-
-
- Verified
-
- clones
-
-
- Verified
-
