-
Notifications
You must be signed in to change notification settings - Fork 10
Network ‐ OVS Interface And Port Found
hoberger-rh edited this page Apr 15, 2026
·
5 revisions
This rule checks if OVS interface and port connection types exist in NetworkManager on OVN-Kubernetes nodes. It verifies that NetworkManager has connections with types ovs-interface (OVS bridge interface) and ovs-port (OVS port)
- OpenShift cluster with OVN-Kubernetes networking
- NetworkManager managing network interfaces
- Open vSwitch installed
- Command:
nmcli
Missing OVS interface or port connections in NetworkManager can cause:
- Network failure after reboot - OVS interfaces don't start automatically
- OVN-Kubernetes initialization failure - OVN cannot configure networking
- Node network isolation - Node loses cluster network connectivity
- Pod communication failure - Pods cannot communicate with other pods
- Node NotReady state - Kubelet cannot connect to API server
This is a critical configuration issue that prevents proper OVN-Kubernetes operation.
Common scenarios causing missing OVS NetworkManager connections:
- Manual connection deletion - Administrator accidentally deleted NetworkManager profiles
- Installation failure - OVN-Kubernetes installation did not complete successfully or NetworkManager profiles not created
- NetworkManager configuration loss - Directory corrupted, filesystem issues, or manual editing caused parse errors
- Upgrade issues - Cluster upgrade failed to preserve OVS NetworkManager profiles or incomplete migration
Check NetworkManager for OVS connection types:
# Filter for OVS connection types (ovs-interface and ovs-port)
nmcli -t -f TYPE connection show | grep ovsThe output should include both ovs-interface and ovs-port connection types.