-
Notifications
You must be signed in to change notification settings - Fork 10
Network ‐ OVS Profile Activation Check
This rule checks if OVS-related NetworkManager profiles are in activated state. It searches for NetworkManager profiles with types ovs-port, ovs-interface, or ovs-bridge and verifies they are activated.
The rule fails if any OVS profile exists but is in deactivated state. Inactive profiles indicate interfaces that should be part of OVS but failed to activate, which can cause network connectivity issues after reboot.
- OpenShift cluster with OVN-Kubernetes networking
- NetworkManager managing network interfaces
- OVS profiles configured in NetworkManager
- Command:
nmcli
Inactive OVS profiles can cause:
- Network failure after reboot - OVS interfaces don't start automatically
- Partial OVS configuration - Some interfaces active, others inactive
- Intermittent connectivity - Inconsistent network state
- OVN datapath incomplete - Missing interfaces break OVN pipeline
- Pod communication failures - Pods cannot communicate properly
- Node degradation - Node may work partially but unreliably
Inactive profiles indicate a configuration that exists but isn't working, which is often more insidious than complete failure.
Common scenarios causing inactive OVS profiles:
- Activation Failures After Reboot
- Manual Deactivation
- Dependency Issues
- Configuration Errors
- OVS Service Issues
Check activation state of OVS NetworkManager profiles:
# List all OVS connections with their activation state
nmcli -t -f TYPE,DEVICE,STATE connection show | grep ovs
# Show all connection details to find inactive ones
nmcli connection show | grep -E "ovs-(port|interface|bridge)"
# Check specific profile state
nmcli connection show <vlan-interface> | grep GENERAL.STATEAll OVS-related profiles (ovs-port, ovs-interface, ovs-bridge) should have STATE=activated.