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.
Another interesting difference/symptom - in /etc/resolv.conf it only adds the domain to the search list, not the extra search lists given by the DHCP server. So I get in /etc/resolv.conf:
# Generated by NetworkManager
search cora.nwra.com
instead of:
# Generated by NetworkManager
search cora.nwra.com nwra.com ad.nwra.com
which is what I get normally when it is brought by NM.
Hello,
Just FYI..We do not plan to fix this issue in RHEL 7. Fixing this in RHEL 7 will be a large effort and undesirable change in behavior.
Thanks!
Sushil
Comment 10Beniamino Galvani
2019-12-09 16:15:28 UTC
I tried to boot RHEL 7.7 and RHEL 8.1 systems with the 'bridge=br0:eth0 rd.neednet=1' kernel commandline and in both cases NetworkManager picked up the connections generated by dracut in /etc/sysconfig/network-scripts/ifcfg-{br0,eth0}. After the boot the DHCP lease was renewed upon expiry and resolv.conf contained the search domain pushed by DHCP. So, I'm unable to reproduce the problem reported in comment 0.
I also tried with static addresses on RHEL 8.1 following the procedure to hardcode the address into the initrd:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/system_design_guide/configuring-automated-unlocking-of-encrypted-volumes-using-policy-based-decryption_system-design-guide
The system come up with the configured addresses and NM correctly took over that configuration. I didn't see any loss of connectivity (which would be a bit surprising because the addresses are static and there is no action needed by NM to maintain network connectivity).
Akhil, can you please set the logging level of NM to 'trace', reproduce the problem and attach journal logs of the boot (journalctl -b)? Please also disable systemd-journald ratelimiting by setting RateLimitIntervalSec=0 in /etc/systemd/journald.conf. Thanks.
FWIW - it seems that if I just boot my EL7.7 system but do not log into the desktop session (KDE in my case) - the network stays up. I'll try to reproduce on EL7.7 with the trace debugging on overnight. I don't yet have a EL8 desktop machine to test with.
With comment 10, this might already be fixed on rhel-8.2 (with the legacy dracut network module).
In rhel-8.3, we will enable NetworkManager in initrd by default (bug 1626348), this backstory of this issue changes entirely (but it also should be fixed).
Moving bug to MODIFIED, so that we can add it to rhel-8.3 errata (and test it).
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (NetworkManager bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4499