This bug was fixed in the package systemd - 249.11-0ubuntu3.9
---------------
systemd (249.11-0ubuntu3.9) jammy; urgency=medium
* udev: gracefully handle rename failures (LP: #2002445)
Files:
- debian/patches/lp2002445/core-device-ignore-failed-uevents.patch
- debian/patches/lp2002445/sd-device-introduce-device_get_property_int.patch
-
debian/patches/lp2002445/sd-device-make-device_set_syspath-clear-sysname-and-sysnu.patch
-
debian/patches/lp2002445/udev-restore-syspath-and-properties-on-failure.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a7ad4a9fc708500c61e3b8127f112d8c90049b2c
systemd (249.11-0ubuntu3.8) jammy; urgency=medium
* network/dhcp4: accept local subnet routes from DHCP (LP: #2004478)
File:
debian/patches/lp2004478-network-dhcp4-accept-local-subnet-routes-from-DHCP.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=96928d5f45ebbfe682b47e842d63506fa0ac9583
* udev: avoid NIC renaming race with kernel (LP: #2002445)
Files:
-
debian/patches/lp2002445/sd-netlink-add-a-test-for-rtnl_set_link_name.patch
-
debian/patches/lp2002445/sd-netlink-do-not-swap-old-name-and-alternative-name.patch
-
debian/patches/lp2002445/sd-netlink-restore-altname-on-error-in-rtnl_set_link_name.patch
-
debian/patches/lp2002445/udev-attempt-device-rename-even-if-interface-is-up.patch
-
debian/patches/lp2002445/udev-net-allow-new-link-name-as-an-altname-before-renamin.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=20dc4d51a340669c26c446c23b5a84516e82ea74
* network: create stacked netdevs after the underlying link is (LP: #2000880)
File:
debian/patches/lp2000880-network-create-stacked-netdevs-after-the-underlying-link-.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ab620e709f3f62eda86af26fd66c00d6e5165a25
* Enable /dev/sgx_vepc access for the group 'sgx' (LP: #2009502)
File:
debian/patches/lp2009502-Enable-dev-sgx_vepc-access-for-the-group-sgx.patch
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=434480ae4059a16ccbde9613be0c26ff1983cc3a
-- Nick Rosbrook <nick.rosbr...@canonical.com> Mon, 20 Mar 2023
10:32:08 -0400
** Changed in: systemd (Ubuntu Jammy)
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/2000880
Title:
systemd-networkd: ActivationPolicy ignored in VLANs
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Jammy:
Fix Released
Status in systemd source package in Kinetic:
Fix Released
Bug description:
[Impact]
The ActivationPolicy property in .network files is ignored for VLANs.
[Test Plan]
* On a Jammy machine with an interface named ens3, create the
following configs:
$ cat > /etc/systemd/network/10-vlan18.netdev << EOF
[NetDev]
Name=vlan18
Kind=vlan
[VLAN]
Id=18
EOF
$ cat > /etc/systemd/network/20-vlan18.network << EOF
[Match]
Name=vlan18
[Network]
Address=10.10.1.1/24
[Link]
ActivationPolicy=manual
EOF
$ cat > /etc/systemd/network/30-ens3.network << EOF
[Match]
Name=ens3
[Network]
DHCP=ipv4
VLAN=vlan18
EOF
* Reboot the machine
* On an affected machine, the vlan18@ens3 interface will have a configured IP
at boot, despite the ActivationPolicy=manual setting in
/etc/systemd/network/20-vlan18.network. On a patched machine, the interface
should not have a configured IP.
[Where problems could occur]
The patch adds a condition where a netdev is not yet ready to be
created. Specifically, it makes sure stacked netdevs are not created
before their underlying link is activated. If we saw any problems, it
would be related to netdev creation.
[Original Description]
This has been fixed upstream, see
Upstream bug: https://github.com/systemd/systemd/issues/22593
Any chance of a backport of the fix to 22.04?
Fix: https://github.com/systemd/systemd-stable/pull/211
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2000880/+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
