[Bug 1931578] Autopkgtest regression report (systemd/247.3-3ubuntu3.2)
Ubuntu SRU Bot
1931578 at bugs.launchpad.net
Fri Jul 9 13:36:42 UTC 2021
All autopkgtests for the newly accepted systemd (247.3-3ubuntu3.2) for hirsute have finished running.
The following regressions have been reported in tests triggered by the package:
umockdev/0.15.4-1 (armhf)
initramfs-tools/0.139ubuntu3 (amd64)
apt/2.2.4ubuntu0.1 (armhf)
netplan.io/0.102-0ubuntu3 (amd64)
Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/hirsute/update_excuses.html#systemd
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
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/1931578
Title:
ActivationPolicy=down causes delay at boot
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Bionic:
Won't Fix
Status in systemd source package in Focal:
Fix Committed
Status in systemd source package in Groovy:
Fix Committed
Status in systemd source package in Hirsute:
Fix Committed
Status in systemd source package in Impish:
Fix Released
Bug description:
[impact]
The ActivationPolicy= parameter was backported in bug 1664844, but
when this is set to down (or always-down or manual) without also
specifying RequiredForOnline=no, then there is a hang at boot waiting
for the network to finish coming online.
[test case]
With the latest systemd, which includes support for ActivationPolicy=,
configure an interface with ActivationPolicy=down and reboot. The boot
will be delayed waiting for that interface.
[regression potential]
any regression would likely cause the system to encounter delay at
boot, or to boot before configured interface(s) are fully online at
boot, or to fail to correctly/fully configure interface(s).
[scope]
this is needed for all releases
this is proposed upstream in:
https://github.com/systemd/systemd/pull/19883
[other info]
this is only needed for convenience, as any configuration using
ActivationPolicy=down can also easily add RequiredForOnline=no
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931578/+subscriptions
More information about the foundations-bugs
mailing list