Description of problem:
We have a customer reporting that he cannot install a RHEL8.3 based system (actually it's RHV4.4, which is based on RHEL8.3) through using a kickstart available on the network, because the bond flips/flops constantly.
Testing showed that RHEL8.2 had not the issue. Additionally, replacing the network-manager dracut module by network-legacy (as used by RHEL8.2) fixes the issue.
It seems that network-manager dracut module (or NetworkManager itself) is not stable enough and cannot be trusted during installation.
I'm hence requesting that we ship a "dual network enabled" initramfs which would let the sysadmin fall back to using network-legacy through some kernel switch for example.
Version-Release number of selected component (if applicable):
8.3 based initrd.img:
- rhel-8.3-x86_64-dvd.iso
- RHVH-4.4-20210202.0-RHVH-x86_64-dvd1.iso
How reproducible:
Always on customer system configuring a bond+vlan at boot.
Right now you can either have network-legacy or NM, there is no way how to have both there. And the patch for this would not be trivial.
Let's move this to NM, to fix the bond issue there.
Comment 5Beniamino Galvani
2021-03-11 19:43:13 UTC
From what I see in logs, the reason why the bond gets disconnected
after 45 seconds is that the interface is configured for
DHCP. Therefore, the issue looks similar to bug 1903698, which is
fixed in NetworkManager-1.26.0-12 (available in z-stream
RHEL-8.3.0.1).
Can you please try a more recent version?
then let's close this as duplicate of bug 1903175 (and bug 1903698, which is the Z-stream for 8.3)
*** This bug has been marked as a duplicate of bug 1903175 ***
Comment 10Marcelo Ricardo Leitner
2021-03-16 14:07:27 UTC