[Bug 1931578] Re: ActivationPolicy=down causes delay at boot

[Dan Streetman]

ubuntu at lp1931578-f:~$ dpkg -l systemd|grep systemd
ii  systemd        245.4-4ubuntu3.7 amd64        system and service manager
ubuntu at lp1931578-f:~$ networkctl status ens8 | grep Activation
     Activation Policy: down                                    
ubuntu at lp1931578-f:~$ networkctl status ens8 | grep Required
ubuntu at lp1931578-f:~$ systemctl status systemd-networkd-wait-online.service 
● systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Sun 2021-07-11 22:15:22 UTC; 4min 1s ago
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 616 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=1/FAILURE)
   Main PID: 616 (code=exited, status=1/FAILURE)

Jul 11 22:13:23 lp1931578-f systemd[1]: Starting Wait for Network to be Configured...
Jul 11 22:13:24 lp1931578-f systemd-networkd-wait-online[616]: managing: ens3
Jul 11 22:15:22 lp1931578-f systemd-networkd-wait-online[616]: Event loop failed: Connection timed out
Jul 11 22:15:22 lp1931578-f systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
Jul 11 22:15:22 lp1931578-f systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
Jul 11 22:15:22 lp1931578-f systemd[1]: Failed to start Wait for Network to be Configured.
ubuntu at lp1931578-f:~$ 

ubuntu at lp1931578-f:~$ dpkg -l systemd|grep systemd
ii  systemd        245.4-4ubuntu3.8 amd64        system and service manager
ubuntu at lp1931578-f:~$ networkctl status ens8 | grep Activation
     Activation Policy: down                                    
ubuntu at lp1931578-f:~$ networkctl status ens8 | grep Required
   Required For Online: no                                      
ubuntu at lp1931578-f:~$ systemctl status systemd-networkd-wait-online.service 
● systemd-networkd-wait-online.service - Wait for Network to be Configured
     Loaded: loaded (/lib/systemd/system/systemd-networkd-wait-online.service; enabled; vendor preset: enabled)
     Active: active (exited) since Sun 2021-07-11 22:26:15 UTC; 44s ago
       Docs: man:systemd-networkd-wait-online.service(8)
    Process: 613 ExecStart=/lib/systemd/systemd-networkd-wait-online (code=exited, status=0/SUCCESS)
   Main PID: 613 (code=exited, status=0/SUCCESS)

Jul 11 22:26:14 lp1931578-f systemd[1]: Starting Wait for Network to be Configured...
Jul 11 22:26:15 lp1931578-f systemd-networkd-wait-online[613]: managing: ens3
Jul 11 22:26:15 lp1931578-f systemd[1]: Finished Wait for Network to be Configured.


** Tags removed: verification-needed verification-needed-focal verification-needed-groovy verification-needed-hirsute
** Tags added: verification-done verification-done-focal verification-done-groovy verification-done-hirsute

-- 
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