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:

NetworkManager-1.22.0-0.2.el8.x86_64 system loses it's IPV4 Address after the lease time expires. 

Also not after to ping other systems or NFS mount volumes after system reboot. Takes as long as 10 minutes to reach remote hosts. Logging in is not an issue 


Version-Release number of selected component (if applicable):

NetworkManager-1.22.0-0.2.el8.x86_64

How reproducible:

After every reboot 


Steps to Reproduce:
1. Boot Machine
2. Test workload and let system stay up for 24 hrs
3. After 24 hours, systems loses it IP Address and need to access console to restart network

Actual results:

Can not log in

Expected results:

Network should stay up for longer periods 

Additional info:

Do not see this issue with NetworkManager-1.22.0-0.1.el8.x86_64 with either losing IP address or mount NFS Volumes after reboot

Here is the message from journalctl where there is a failure
Dec 17 10:34:24 perf2.perf.lab.eng.bos.redhat.com NetworkManager[1851]: <info>  [1576596864.7568] dhcp4 (eno3): state changed bound -> expire
Dec 17 10:34:24 perf2.perf.lab.eng.bos.redhat.com NetworkManager[1851]: <info>  [1576596864.9608] device (eno3): DHCPv4: 480 seconds grace period started

Created attachment 1646789 [details]
Reproducer script

Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/368

I was also seeing this problem, and I can't replicate it anymore after updating to 1.22.8-4.el8

for rhel-8.2, we will change the implementation of the default DHCP plugin.
From a systemd based DHCP client to a nettools based one.

Initially there were some issues, I believe these are all fixed in recent rhel-8.2 builds.


If you have new DHCP related issues with a recent rhel-8.2 build, please open a new bug. It very likely has different underlying causes.

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, 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:1847

Created attachment 1689672 [details]
tcpdump.log.bz2