Bug 2072040 - configure-ovs: delays boot waiting for patch port to be unmanaged
Summary: configure-ovs: delays boot waiting for patch port to be unmanaged
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: Unspecified
OS: Unspecified
medium
low
Target Milestone: ---
: 4.11.0
Assignee: Jaime Caamaño Ruiz
QA Contact: Ross Brattain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-05 13:23 UTC by Jaime Caamaño Ruiz
Modified: 2022-12-24 18:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-06 08:32:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift machine-config-operator pull 3059 0 None open Bug 2072040: Avoid NM managing patch port between br-int and br-ex 2022-04-05 13:28:52 UTC
Github openshift machine-config-operator pull 3120 0 None open Bug 2078866: configure-ovs: avoid restarting NetworkManager 2022-05-06 08:32:51 UTC

Description Jaime Caamaño Ruiz 2022-04-05 13:23:23 UTC 
Description of problem:

configure-ovs resets network configuration on boot, and while doing so waits for all devices to become unmanaged in NetworkManager. Currently the patch port between br-int and br-ex created by ovn-kubernetes is managed by NetworkManager, never becomes unmanaged and causes an accumulated delay of 2 minutes on boot.

This patct port should never be managed by NetworkManager.
Note You need to log in before you can comment on or make changes to this bug.