[Bug 1642903] Re: introduce disk/by-id (model_serial) symlinks for NVMe drives
Launchpad Bug Tracker
1642903 at bugs.launchpad.net
Thu Dec 15 00:11:27 UTC 2016
This bug was fixed in the package systemd - 229-4ubuntu13
---------------
systemd (229-4ubuntu13) xenial; urgency=medium
[ Martin Pitt ]
* Backport graphical-session{,-pre}.target user units, for future usage from
snaps. (LP: #1640293)
* debian/rules: Clean up *.busname units. They are useless in 16.04 as they
will always be "condition failed" as kdbus has never existed. But they add
ordering constraints which make it impossible to start
systemd-networkd.service during early boot, which is an upcoming
requirement for cloud-init. (Part of LP: #1636912)
* Drop systemd-networkd's "After=dbus.service" ordering so that it can start
during early boot (for cloud-init.service). It will auto-connect to D-Bus
once it becomes available later, and transient (from DHCP) hostname and
timezone setting do not work in 16.04 anyway. (LP: #1636912)
[ Dan Streetman ]
* rules: introduce disk/by-id (wwid and model_serial) symlinks
for NVMe drives (LP: #1642903)
-- Martin Pitt <martin.pitt at ubuntu.com> Thu, 24 Nov 2016 12:41:23
+0100
** Changed in: systemd (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1642903
Title:
introduce disk/by-id (model_serial) symlinks for NVMe drives
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Trusty:
In Progress
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Yakkety:
Fix Released
Status in systemd source package in Zesty:
Fix Released
Bug description:
[Impact]
NVMe drives can't be identified/accessed via /dev/disk/by-id/nvme-
SERIAL symlinks.
[Test Case]
On a system with an NVMe drive, check the /dev/disk/by-id/ directory;
with the patch, it will contain link(s) named by the drive serial
number. This should be the *only* change in `ls -l /dev/disk/*/*`.
On a system without NVMe, verify that `ls -l /dev/disk/*/*` is
identical (aside from dates, of course) before and after the upgrade
to the -proposed version.
[Regression Potential]
Errors in udev rules can lead to an unbootable or otherwise completely
broken system if they unintentionally break or clobber existing
/dev/disks/ symlinks.
[Other Info]
This patch is already included upstream and in zesty systemd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1642903/+subscriptions
More information about the foundations-bugs
mailing list