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.
Description of problem:
Every few days/weeks one of our servers loses network and the journal shows:
Jul 07 13:33:56 gold.esat.kuleuven.be NetworkManager[989]: <error> [1594121636.0006] dhcp4 (ens3): error -111 dispatching events
Jul 07 13:33:56 gold.esat.kuleuven.be NetworkManager[989]: <info> [1594121636.0015] dhcp4 (ens3): state changed extended -> fail
Jul 07 13:33:56 gold.esat.kuleuven.be NetworkManager[989]: <info> [1594121636.0019] device (ens3): DHCPv4: trying to acquire a new lease within 90 seconds
Jul 07 13:35:26 gold.esat.kuleuven.be NetworkManager[989]: <info> [1594121726.1552] device (ens3): DHCPv4: grace period expired
Jul 07 14:34:08 gold.esat.kuleuven.be NetworkManager[989]: <info> [1594125248.7449] agent-manager: agent[866756f0a2afecf7,:1.40116/nmcli-connect/0]: agent registered
Jul 07 14:34:08 gold.esat.kuleuven.be NetworkManager[989]: <info> [1594125248.8192] device (ens3): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Jul 07 14:34:08 gold.esat.kuleuven.be NetworkManager[989]: <info> [1594125248.8290] manager: NetworkManager state is now DISCONNECTING
Our interface has a static IPv6 address and uses DHCP for IPv4. Only the IPv4 address is lost.
It seems the fix from https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c5d1d4c498c50dfc7d2d18b213a117dd1199f1de is missing?
https://bugzilla.redhat.com/show_bug.cgi?id=1829178 also looks similar.
Version-Release number of selected component (if applicable):
NetworkManager-1.22.8-4.el8.x86_64
How reproducible:
Seems to happen every few days since upgrade to 8.2. Never had this issue with 8.1
Steps to Reproduce:
1.
2.
3.
Actual results:
IPv4 address is removed from interface
Expected results:
IPv4 lease is extended.
Additional info: