http://bugzilla.suse.com/show_bug.cgi?id=980303 http://bugzilla.suse.com/show_bug.cgi?id=980303#c2 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hare@suse.com Flags| |needinfo?(hare@suse.com) --- Comment #2 from Sebastian Parschauer --- Created attachment 677246 --> http://bugzilla.suse.com/attachment.cgi?id=677246&action=edit Patch: fix the persistent storage udev rules for NVMe I've looked at /run/systemd/generator/systemd-cryptsetup@cr_nvme.service and it relies on a symlink /dev/disk/by-id/nvme-20025386261008f3a-part5 which is not there. I've found the bug in /lib/udev/rules.d/60-persistent-storage.rules not creating the required symlinks. So I've fixed that udev rule with the attached patch. Hannes: Could you please review the attached patch and take it over to the respective package so that it will be in place for others as well? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980303 http://bugzilla.suse.com/show_bug.cgi?id=980303#c4 Sebastian Parschauer changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |CONFIRMED Found By|--- |L3 Assignee|bnc-team-screening@forge.pr |systemd-maintainers@suse.de |ovo.novell.com | Target Milestone|--- |Leap 42.1 --- Comment #4 from Sebastian Parschauer --- Assigning to the systemd maintainers to fix this. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980303 http://bugzilla.suse.com/show_bug.cgi?id=980303#c6 Thomas Blume changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thomas.blume@suse.com Flags| |needinfo?(hare@suse.com) --- Comment #6 from Thomas Blume --- (In reply to Hannes Reinecke from comment #3)

Well. We've had similar reports here (bug#944132, bug#928391), so I'm surprised they haven't been ported to Leap... However, I really would think this is the wrong way to handle it. Thing is, NVMe devices should be using the eui name provided by the NVMe device itself, and not rely on the (fake) SCSI ID to be present. The SCSI ID one can be compiled out (it's been moved to a module), so you might end up with an NVMe device which does _not_ provide a SCSI interface at all.

Oops, this was a mistake from another commit which was a bit too aggressive. Meanwhile upstream has added nvme support. Upstream commit: 427a28ecbe0eb170e651e0530ab58d6e6f6c498c shows: -->-- +# NVMe +KERNEL=="nvme*[0-9]n*[0-9]", ATTR{wwid}=="?*", SYMLINK+="disk/by-id/nvme-$attr{wwid}" +KERNEL=="nvme*[0-9]n*[0-9]p*[0-9]", ENV{DEVTYPE}=="partition", ATTRS{wwid}=="?*", SYMLINK+="disk/by-id/nvme-$attr{wwid}-part%n" + --<-- Hannes, is this the eui you've mentioned? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=980303 http://bugzilla.suse.com/show_bug.cgi?id=980303#c14 --- Comment #14 from Bernhard Wiedemann --- This is an autogenerated message for OBS integration: This bug (980303) was mentioned in https://build.opensuse.org/request/show/427000 13.1 / systemd -- You are receiving this mail because: You are on the CC list for the bug.