Bug 1308795
Summary: | /dev/disk/by-id/wwn-* links for SATA devices have words in reverse order | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | nikhil kshirsagar <nkshirsa> | |
Component: | systemd | Assignee: | systemd-maint | |
Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> | |
Severity: | medium | Docs Contact: | Lucie Vařáková <lmanasko> | |
Priority: | unspecified | |||
Version: | 7.2 | CC: | amulhern, bdonahue, bgoncalv, bmarzins, coughlan, fge, fsumsal, jmagrini, jscotka, lilin, lnykryn, msekleta, nkshirsa, systemd-maint-list, systemd-maint | |
Target Milestone: | rc | Keywords: | ZStream | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | systemd-219-20.el7 | Doc Type: | Release Note | |
Doc Text: |
A fix for systemd to read the device identification bytes correctly
Due to an endianness problem, the version of systemd in Red Hat Enterprise Linux 7.2 read the device identification bytes in a wrong order, causing the `dev/disk/by-id/wwn-*` symbolic links to be generated incorrectly. A patch has been applied to put the device identification bytes in the correct order and the symbolic links are now generated correctly. Any reference that depends on the value obtained from `/dev/disk/by-id/wwn-*` needs to be modified to work correctly in Red Hat Enterprise Linux 7.3 and later.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1311887 (view as bug list) | Environment: | ||
Last Closed: | 2016-11-04 00:51:55 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1203710, 1289485, 1311887 |
Description
nikhil kshirsagar
2016-02-16 06:28:18 UTC
pushed to staging https://github.com/lnykryn/systemd-rhel/commit/d1c32b69edc7f0f62a7c3f65691c2cb9fedcb112 https://github.com/lnykryn/systemd-rhel/commit/2a62c3c66698148f1439176bd6ca5a946b8de550 -> POST *** Bug 1273306 has been marked as a duplicate of this bug. *** If the customer is interested to test the fix, here is a test build of currently staged patches for 7.3 which also includes fix for this issue. https://copr.fedorainfracloud.org/coprs/lnykryn/systemd-rhel-staging/ committed to master branch -> https://github.com/lnykryn/systemd-rhel/commit/a405c6309d143b998197141b3531201ed07d56d9 https://github.com/lnykryn/systemd-rhel/commit/e38ebe01cbc1f415a067e96d0373ad22944b3e70 -> modified It is important to notify users of this change in the RHEL 7.2 API. I have copied the Doc Text from the 7.2.z BZ here, with some modifications. Please review. This should be included prominently in the 7.3 Release Notes, IMO. Ben, will this impact automatically generated multipath user friendly names, or does multipath get the WWID from another source? (Thanks, Mulhern, for pointing out this issue.) (In reply to Tom Coughlan from comment #15) > > Ben, will this impact automatically generated multipath user friendly names, > or does multipath get the WWID from another source? That depends. Lukáš, does this effect the value of ID_SERIAL in the udev database (or ID_UID, which we use for dasd devices)? If not, then multipath device names shouldn't be effected. From the code it looks that those variables should not be affected. Barry, Please develop a test for this in 7.3 dm-multipath. The test summary is: install 7.2 with dm-multipath and user friendly names. Observe that the WWID in /dev/disk/by-id/wwn-* is incorrect. Take a look at the automatically generated mapping from mpathn to WWID. Hopefully it is the correct WWID. Update to 7.3. Observe that the WWID in /dev/disk/by-id/wwn-* is now correct. Make sure the mpathn mapping is correct and unchanged. Nikhil, Please follow-up on comments 12, 13. Is this resolved? Tom I have sent an email out to the team. We will decide who will create the test case and put it into our 7.3 test plan. Verified with systemd-219-30.el7. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: /dev/disk/by-id/wwn-* links' word order :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ 06:19:09 ] :: [ INFO ] :: Current ID: 5000c5004ef448e7 :: [ 06:19:09 ] :: [ INFO ] :: Expected ID: 5000c5004ef448e7 :: [ BEGIN ] :: If both IDs are empty, the machine doesn't have any SATA disk connected... :: actually running '[[ ! -z '5000c5004ef448e7' && ! -z '5000c5004ef448e7' ]]' :: [ PASS ] :: If both IDs are empty, the machine doesn't have any SATA disk connected... (Expected 0, got 0) :: [ BEGIN ] :: Running '[[ '5000c5004ef448e7' == '5000c5004ef448e7' ]]' :: [ PASS ] :: Command '[[ '5000c5004ef448e7' == '5000c5004ef448e7' ]]' (Expected 0, got 0) Where current and expected IDs are following: CURRENT_ID=$(udevadm info -p /sys/class/block/sda | grep "ID_WWN=" | sed -re 's/.*ID_WWN=0x(.+)/\1/') EXPECTED_ID=$(hdparm -I /dev/sda | grep WWN | sed -re 's/.+ Identifier: (.+)/\1/') 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, 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://rhn.redhat.com/errata/RHBA-2016-2216.html |