My nic had it installed and it raced with systemd-networkd because our baseconfig provides configs for both managers
Sent from my iPhone > On Jun 19, 2020, at 20:43, Andrew Cagney <[email protected]> wrote: > > > > >>> On Fri, 19 Jun 2020 at 18:00, Paul Wouters <[email protected]> wrote: >>> On Thu, 18 Jun 2020, Andrew Cagney wrote: >>> >>> > >>> > Rebuilding the testing VMs seems to have introduced a failure vis: >>> > >>> > pre-rebuild:https://testing.libreswan.org/v3.30-1022-g4bd4d18c0f-master/newoe-04-pass-pass/OUTPUT/ >>> > >>> > post-rebuild (which has the effect of upgrading everything): >>> > https://testing.libreswan.org/v3.30-1023-g5e4995c608-master/newoe-04-pass-pass/OUTPUT/road.console.diff >>> > yes consecutive commits and nothing changed. >>> > >>> > the key difference, I'm assuming, is the kernel (however, it could be >>> > something else). >>> >>> It is caused by nic losing the IP info on its eth1. >>> Which is because it is racing with eth0. Since it tries to add the route >>> to a network for which it needs eth0, eth1 fails. Then eth0 establishes. >>> >>> I think the race is caused by having NetworkManager and systemd-networkd. >>> On nic, run: rpm -e NetworkManager >> >> I'm not so sure. >> >> f32.ks already excludes it during the initial install and only a select list >> of packages is updated (NetworkManager isn't on the list). So adding >> NetworkManager to the exclude list is just a safety net. >> >> This run, which is working, >> https://testing.libreswan.org/v3.30-1044-gb7aa1cdd94-master/ >> has everything on the short update list except the kernel & xl2tpd. >> >> And, locally where things failed, NetworkManager isn't installed. >> >> >> That fixed it for me on my laptop. >> >> Paul
_______________________________________________ Swan-dev mailing list [email protected] https://lists.libreswan.org/mailman/listinfo/swan-dev
