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.
DescriptionFernando F. Mancera
2022-06-07 13:51:21 UTC
This is a clone of https://bugzilla.redhat.com/show_bug.cgi?id=2077605 for RHEL 9.1
In OpenShift, we rebased on RHEL 8.6 and saw failures to install with ovn-kubernetes. Oddly, this only happens on Azure some of the time.
However, what appears to happen after restarting NetworkManager very rapidly after getting a lease, we DHCP again but the interface never gets the IP. The logs say "ip4: set state fail (was pending, reason: check-ip-state)" -- what is check-ip-state?
I will attach a while journal, but the timeline I've pieced together looks like this:
**** 14:00:54 Start NM
Apr 21 14:00:54 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg configure-ovs.sh[1742]: + systemctl restart NetworkManager
**** 14:00:54 We got a DHCP lease
Apr 21 14:00:54 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg systemd[1]: NetworkManager-wait-online.service: Succeeded.
[...]
Apr 21 14:00:54 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2153]: <debug> [1650549654.8062] dhcp4 (eth0): option ip_address => '10.0.128.6'
**** 14:00:54 Network Manager shut down again....
Apr 21 14:00:54 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg systemd[1]: Stopping Network Manager...
Apr 21 14:00:54 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2153]: <info> [1650549654.8070] caught SIGTERM, shutting down normally.
**** 14:00:54 Starting again....
Apr 21 14:00:54 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg systemd[1]: Starting Network Manager...
**** 14:00:55 Try to DHCP again
Apr 21 14:00:55 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2753]: <debug> [1650549655.0340] dhcp4 (eth0): send REQUEST to 255.255.255.255
**** 14:00:55 Get a lease again
Apr 21 14:00:55 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2753]: <debug> [1650549655.0492] dhcp4 (eth0): option ip_address => '10.0.128.6'
**** 14:00:55 But NetworkManager doesn't apply it to the interface
Apr 21 14:00:55 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2753]: <debug> [1650549655.0505] device[e1c2da34f52474c2] (eth0): ip:dhcp4: set state fail (was pending)
Apr 21 14:00:55 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2753]: <debug> [1650549655.0509] device[e1c2da34f52474c2] (eth0): ip4: set state fail (was pending, reason: check-ip-state)
[...]
Apr 21 14:01:15 ci-ln-v6m988k-002ac-p4b5q-worker-centralus2-r4mkg NetworkManager[2753]: <debug> [1650549675.0392] device[e1c2da34f52474c2] (eth0): ip4: required-timeout: expired
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-2022:8265