Bug 1627820
| Summary: | dracut configured bridge interface does not stay up | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Orion Poplawski <orion> |
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 8.1 | CC: | atragler, bgalvani, fgiudici, fpokryvk, jmaxwell, lrintel, rkhan, sukulkar, thaller, tpelka, vbenes |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.1 | ||
| Hardware: | x86_64 | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-1.25.1-1.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-11-04 01:48:18 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1626348, 1715493 | ||
| Bug Blocks: | 1701002, 1955571 | ||
|
Description
Orion Poplawski
2018-09-11 14:59:32 UTC
It also seems like this problem started when I shifted to a bridged interface. When I just had eth0, the network stayed up fine. 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. This depends on dracut patches (https://bugzilla.redhat.com/show_bug.cgi?id=1715493) that are not in yet.. Moving this to 8.2. Taking it out of the RPL. -Sushil Going to be solved with RHEL 8.2 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 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. Well, the connection stayed up overnight, so perhaps this has been resolved. Taking this off of the RPL. We will revisit in 8.3 once we hear back and if it needs any action from us. -Sushil 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). Dropping from RPL-8.3. This is already fixed upstream, and thus will be automatically get in with the rebase in RHEL-8.3 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 |