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.
Bug 1841937 - NetworkManager doesn't reconnect after DHCP failure
Summary: NetworkManager doesn't reconnect after DHCP failure
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Thomas Haller
QA Contact: Desktop QE
URL:
Whiteboard:
: 1843052 (view as bug list)
Depends On: 1829178
Blocks: 1843357
TreeView+ depends on / blocked
 
Reported: 2020-05-29 21:10 UTC by John W. Lamb
Modified: 2023-10-06 20:20 UTC (History)
27 users (show)

Fixed In Version: NetworkManager-1.25.2-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1829178
: 1843357 (view as bug list)
Environment:
Last Closed: 2020-11-04 01:49:42 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
output of "journalctl -u NetworkManager -b" (51.39 KB, text/plain)
2020-05-29 21:10 UTC, John W. Lamb 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-933 0 None None None 2023-10-06 20:20:19 UTC
Red Hat Knowledge Base (Solution) 5188461 0 None None None 2020-06-29 15:32:58 UTC
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:50:19 UTC

Description John W. Lamb 2020-05-29 21:10:43 UTC 
Created attachment 1693531 [details]
output of "journalctl -u NetworkManager -b"

Description of problem:
I ran "dnf update" and rebooted. After almost 20 hours, an error from the dhcp4 component caused the network connection to drop, and no reconnection was attempted.

Version-Release number of selected component (if applicable):
[root@devservices-ha ~]# rpm -q NetworkManager
NetworkManager-1.22.8-4.el8.x86_64
[root@devservices-ha ~]# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.2 (Ootpa)

How reproducible:
Can't be reproduced by hand

Steps to Reproduce:
1.
2.
3.

Actual results:
[root@devservices-ha ~]# journalctl -uNetworkManager
...
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): option requested_static_routes => '1'
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): option requested_subnet_mask => '1'
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): option requested_time_offset => '1'
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): option requested_wpad       => '1'
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): option routers              => '10.17.225.254'
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): option subnet_mask          => '255.255.254.0'
May 28 07:42:10 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590676930.6748] dhcp4 (lanbr0): state changed extended -> extended
May 29 03:22:13 devservices-ha.dpp.openshift.com NetworkManager[1738]: <error> [1590747733.5661] dhcp4 (lanbr0): error -111 dispatching events
May 29 03:22:13 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590747733.5665] dhcp4 (lanbr0): state changed extended -> fail
May 29 03:22:13 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590747733.5665] device (lanbr0): DHCPv4: trying to acquire a new lease within 90 seconds
May 29 03:23:43 devservices-ha.dpp.openshift.com NetworkManager[1738]: <info>  [1590747823.7943] device (lanbr0): DHCPv4: grace period expired

[root@devservices-ha ~]# nmcli                                                                                                                                                                                                                
lanbr0: connected to lanbr0                                                                                                                                                                                                                   
        "lanbr0"                                                                                                                                                                                                                              
        bridge, 00:25:90:FD:74:CD, sw, mtu 1500                                                                                                                                                                                               
        ip4 default, ip6 default                                                                                                                                                                                                              
        inet6 2620:52:0:11e0:9e6b:985a:3ef1:187e/64                                                                    
        inet6 fe80::e109:a60c:ad4d:4f5f/64                                                                             
        route6 2620:52:0:11e0::/64                                                                                     
        route6 ::/0                                                                                                                                                                                                                           
        route6 fe80::/64                                                                                                                                                                                                                      
        route6 ff00::/8                                                                                                                                                                                                                       
...

*** ^Note there's no "inet4" address line

Expected results:
NetworkManager should attempt to reconnect, and the "lanbr0" connection should have an inet4 address:

[root@devservices-ha ~]# nmcli
lanbr0: connected to lanbr0
        "lanbr0"
        bridge, 00:25:90:FD:74:CD, sw, mtu 1500
        ip4 default, ip6 default
        inet4 10.17.225.43/23
        route4 0.0.0.0/0
        route4 10.17.224.0/23
        inet6 2620:52:0:11e0:9e6b:985a:3ef1:187e/64
        inet6 fe80::e109:a60c:ad4d:4f5f/64
        route6 2620:52:0:11e0::/64
        route6 ::/0
        route6 ff00::/8
        route6 fe80::/64

Additional info:
This seems like the same problem as https://bugzilla.redhat.com/show_bug.cgi?id=1829178

I discussed the issue with thaller in IRC, and he agreed that this looks like the same issue

+++ This bug was initially created as a clone of Bug #1829178 +++

Description of problem:

31 was ok. updated my desktop to 32 today.
using dhcp in my home net. "dhcp-server-router: PC yet running f31.
periodically, each few minutes, dhcp client crushing and restarting network connection, closing all connections to router.

my network card is integrated:
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31)
	Subsystem: ASUSTeK Computer Inc. Device 8672
	Flags: bus master, fast devsel, latency 0, IRQ 126
	Memory at f7100000 (32-bit, non-prefetchable) [size=128K]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] PCI Advanced Features
	Kernel driver in use: e1000e
	Kernel modules: e1000e

adding screenshots

--- Additional comment from  on 2020-04-29 06:29:31 UTC ---



--- Additional comment from Pavel Zhukov on 2020-04-29 06:47:52 UTC ---

Nothing to do with dhcp here. Reassigning to proper component

--- Additional comment from  on 2020-04-29 06:59:05 UTC ---

and another one journal screenshot. starting from line, I guess, "grace period expired"

--- Additional comment from  on 2020-04-29 06:59:31 UTC ---



--- Additional comment from Beniamino Galvani on 2020-04-29 07:02:35 UTC ---

Can you please do the following (as root user):

 - edit /etc/NetworkManager/NetworkManager.conf and set level=TRACE in the [logging] section
 - set "RateLimitIntervalSec=0" in /etc/systemd/journald.conf
 - reboot
 - wait that the problem happens again
 - attach the output of 'journalctl -u NetworkManager -b' to this bugzilla

After attaching the journal log, you could change the DHCP plugin
used by NM to solve your issue. To do this, set 'dhcp=dhclient' or
'dhcp=systemd' in the [main] section of /etc/NetworkManager/NetworkManager.conf.
Then restart NM with 'systemctl restart NetworkManager'.

Thank you!

--- Additional comment from  on 2020-04-29 07:21:21 UTC ---

with asked settings right after this error

--- Additional comment from Beniamino Galvani on 2020-04-29 07:29:59 UTC ---

(In reply to animuspexus from comment #6)
> Created attachment 1682736 [details]
> screenshot 3
> 
> with asked settings right after this error

Unfortunately the log doesn't fit in one screen. Could you instead do:

 journalctl -u NetworkManager -b > log.txt

and attach the log.txt file? If you didn't reboot since then, you don't need to perform again the previous steps.

--- Additional comment from  on 2020-04-29 08:36:36 UTC ---

I didn't rebooted. changed to dhcp=system after uploaded last screenshot (this helped). complete log, includingly screenshoted timings, is in attachment.

--- Additional comment from Beniamino Galvani on 2020-04-29 16:55:22 UTC ---

Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/486
Comment 4 Thomas Haller 2020-06-03 15:05:27 UTC 
*** Bug 1843052 has been marked as a duplicate of this bug. ***
Comment 7 Vladimir Benes 2020-06-15 13:13:05 UTC 
covered by:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/577
Comment 10 errata-xmlrpc 2020-11-04 01:49:42 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.