[Swan-dev] Kernel 5.6.18-300.fc32.x86_64 VS Kernel 5.6.14-300.fc32.x86_64
andrew.cagney at gmail.com
Sat Jun 20 00:42:57 UTC 2020
On Fri, 19 Jun 2020 at 18:00, Paul Wouters <paul at nohats.ca> wrote:
> On Thu, 18 Jun 2020, Andrew Cagney wrote:
> > Rebuilding the testing VMs seems to have introduced a failure vis:
> > pre-rebuild:
> > post-rebuild (which has the effect of upgrading everything):
> > 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,
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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Swan-dev