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: After rebooting a switch we see that interfaces configured with NMstate are not automatically reconnected. 

This is a clone of https://issues.redhat.com/browse/OCPBUGS-14170 since it seems to be more related to NetworkManager than any OpenShift component.

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


How reproducible:


Steps to Reproduce:
1.Configure interfaces using NodeNetworkConfigurationPolicy from Kubernetes-NMState
2.Reboot the switch to which interfaces are connected
3.Check if the interfaces have an IP

Actual results: Interface are up, but they have no IP


Expected results: Interface should have an IP & usable


Additional info: As a workaround customer reboots the node or runs --> nmcli con up

Sure @sfaye 

Thanks for informing this. Please close this bug marking duplicate

*** This bug has been marked as a duplicate of bug 2207690 ***