Re: workaround for systemd-networkd-wait-online boot fail/delay on systems with bridge for v234? (fix @ systemd/issues/2154 requires v>242)

[PGNet Dev <pgnet.dev@xxxxxxxxx>]

On 6/16/20 1:35 AM, Lennart Poettering wrote:
> On Sa, 30.05.20 18:02, PGNet Dev (pgnet.dev@xxxxxxxxx) wrote:
> 
>> 	IS there a backport of this^^ fix available for v234 that popped up in the meantime?
>>
>> 	If not, as is likely, is there a "safe" workaround for quieting the fail, and rm'ing the associated boot delay?  Is rm'ing either the "Also=" or "WantedBy=" a reasonable band-aid?
>>
>> 	Or, some other approach?
> 
> You could use RequiredForOnline= in the bridge's .network file to mark
> it as irrelevant for systemd-network-wait-online.
> 
> Lennart
> 
> --
> Lennart Poettering, Berlin

On my current machine, just upgraded to new OS version (still same distro -- for the moment) I've,

 networkctl
 IDX LINK             TYPE               OPERATIONAL SETUP
   1 lo               loopback           carrier     unmanaged
   2 enp3s0           ether              no-carrier  configuring
   3 enp5s0           ether              routable    configured

infc #3 is active; intfc #2 is unused

I added to each


cd /etc/systemd/network
grep Link -A1 *
 20-enp3s0.network:[Link]
 20-enp3s0.network-RequiredForOnline=no
 --
 20-enp5s0.network:[Link]
 20-enp5s0.network-RequiredForOnline=no


and rebooted.

still, there's a 2min delay on startup

systemd-analyze blame | head
      2min 284ms systemd-networkd-wait-online.service
          5.803s dkms.service
          5.409s rc-local.service
          4.270s mariadb-custom.service
          3.952s after-local.service
          3.647s udisks2.service
          2.985s rpcbind.service
          2.936s mcelog.service
          2.901s ca-certificates.service
          2.878s smartd.service

in dmesg,

 dmesg | grep wait-online -A1 -B1
  [  129.299191] systemd[1]: Started update geoipdb service.
  [  130.961418] systemd-networkd-wait-online[1664]: Event loop failed: Connection timed out
  [  130.971019] systemd[1]: systemd-networkd-wait-online.service: Main process exited, code=exited, status=1/FAILURE
  [  130.971276] systemd[1]: Failed to start Wait for Network to be Configured.
  [  130.974180] systemd[1]: systemd-networkd-wait-online.service: Unit entered failed state.
  [  130.974187] systemd[1]: systemd-networkd-wait-online.service: Failed with result 'exit-code'.
  [  130.974266] systemd[1]: Reached target Network is Online.

other than the two interfaces I _do_ have -- and have set

 [Link]
 RequiredForOnline=no

for, what's possibly _still_ causing this delay?

this^ is, as before, with

 rpm -qa | grep ^systemd-2
  systemd-234-lp152.30.1.x86_64

switching back to non-systemd-networkd network stack eliminates any such delay.
not surprising, given the bug -- and certainly not ideal.
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel