This bug was fixed in the package systemd - 252.5-2ubuntu3.1
---------------
systemd (252.5-2ubuntu3.1) lunar; urgency=medium
* debian/tests/tests-in-lxd: use --reuse flag in lxc publish (LP: #2023229)
File: debian/tests/tests-in-lxd
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2a443ddd5b67596647e463eee64d58c3c71bbf08
* udev-rules: fix nvme symlink creation on namespace changes (LP: #2028180)
File:
debian/patches/lp2028180-udev-rules-fix-nvme-symlink-creation-on-namespace-changes.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=064c7c00aa133b697ab3c0082b825e2f197f91cc
* core: reorder systemd arguments on reexec (LP: #2013543)
File:
debian/patches/lp2013543-core-reorder-systemd-arguments-on-reexec.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=45541ccbc16ed30b6a120cda7401f69cce164d54
* network/dhcp4: do not ignore the gateway even if the destination is in same
network (LP: #2009743)
Files:
-
debian/patches/lp2009743/network-dhcp4-do-not-ignore-the-gateway-even-if-the-desti.patch
-
debian/patches/lp2009743/test-network-add-one-more-testcase-for-DHCPv4-classless-r.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ddea3bcbca3421299b13cfe897157cfbf9f0f06d
* debian/systemd.postint: do not daemon re-exec if we could hit LP: #2013543
File: debian/systemd.postinst
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=e1a08bb427e19ced6c16f054ebdee43ccbc9c528
* Drop debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch (LP:
#1982218)
File:
debian/patches/debian/UBUNTU-wait-online-exit-if-no-links-are-managed.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8235427fd8859ee393a08d425e1a52e1ebcbe2f1
* sd-bus: bus_message_type_from_string is not pure (LP: #2031683)
File:
debian/patches/lp2031683-sd-bus-bus_message_type_from_string-is-not-pure.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=2d65b6c74864976a2bb42c884baf75d1674215fc
-- Nick Rosbrook <en...@ubuntu.com> Fri, 18 Aug 2023 14:15:03 -0400
** Changed in: systemd (Ubuntu Lunar)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2028180
Title:
[SRU][Ubuntu 22.04] Duplicate link for NVMe device by-id
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Jammy:
Fix Released
Status in systemd source package in Kinetic:
Won't Fix
Status in systemd source package in Lunar:
Fix Released
Status in systemd source package in Mantic:
Fix Released
Bug description:
[Impact]
When working with NVMe/TCP host functionality, connecting to NVMe
subsystem through multiple controllers can lead to an invalid device
link created in /dev/disc/by-id/ being created.
Steps to reproduce:
Step 1: Install Ubuntu 22.04 LTS (ubuntu-22.04.1-live-server-amd64) on system.
Step 2: Install nvme-cli package, currently installed version is nvme version
1.16
Step 3: In the os terminal, type any nvme connect-all to connect to NVMe
subsystems and check the duplicate entries in /dev/disk/by-id/.
This may cause users to choose the wrong link and would not be able to
work with it.
[Fix]
udev-rules: fix nvme symlink creation on namespace changes
https://github.com/systemd/systemd/commit/c5ba7a2a4dd19a2d31b8a9d52d3c4bdde78387f0
[Test Plan]
Connect to NVMe/TCP subsystem using nvme connect-all. This was tested against
a few Dell Storage systems.
Steps to Reproduce:
1. Use nvme connect-all to connect to an NVMe/TCP subsystems
2. Check /dev/disk/by-id. The symlinks for NVMe devices should have the
namespace id appended to them. E.g., if there is /dev/disk/by-id/nvme-$FOO,
there should be a /dev/disk/by-id/name-$FOO_$ID.
[ Where problems could occur ]
This issue may be experienced by users who use NVMe/TCP solutions.
Regression risk is low, because the existing symlink pattern is kept for
backwards compatibility. This patch adds a new symlink pattern that includes
the namespace ID, which will remain persistent throughout a boot.
[ Other Info ]
Expected Behavior:
No duplicate entries of NVMe subsystems should exist.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2028180/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
