Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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

Can we clear the z-stream request here then?

Yes, sure.