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):
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
Can not log in
Network should stay up for longer periods
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: <info> [1576596864.7568] dhcp4 (eno3): state changed bound -> expire
Dec 17 10:34:24 perf2.perf.lab.eng.bos.redhat.com NetworkManager: <info> [1576596864.9608] device (eno3): DHCPv4: 480 seconds grace period started
Created attachment 1646789 [details]
Upstream merge request:
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.
Created attachment 1689672 [details]