-
Bug
-
Resolution: Done
-
Major
-
4.12.0
-
None
-
None
-
SDN Sprint 228, SDN Sprint 229, SDN Sprint 230
-
3
-
Rejected
-
False
-
Description of problem:
For Hardware Backed Management Ports (e.g. Virtual functions), the Egress IP Health Check Feature will error out with: "unable to start health checking server: no mgmt ip"
Version-Release number of selected component (if applicable):
OVN-Kubernetes 4.12.0
How reproducible:
Always
Steps to Reproduce:
1. Load OVN-Kubernetes 4.12.0 in MLX BlueField 2 2. If in NIC mode: https://github.com/ovn-org/ovn-kubernetes/pull/3160 https://github.com/ovn-org/ovn-kubernetes/pull/3251 Patches are needed. 3. If in DPU mode then those above patches are optional. 4. Set OVNKUBE_NODE_MGMT_PORT_NETDEV environment variable to point to the Virtual Function.
Actual results:
Error in ovnkube-node: "unable to start health checking server: no mgmt ip". The ovnkube-node container will crash. Egress IP Health Check should be compatible with VFs as management port.
Expected results:
No Error.
Additional info:
A simple workaround is to not return an error: go-controller/pkg/node/node.go @@ -660,7 +660,8 @@ func (n *OvnNode) startEgressIPHealthCheckingServer(wg *sync.WaitGroup, mgmtPort return fmt.Errorf("failed start health checking server due to unsettled IPv6: %w", err) } } else { - return fmt.Errorf("unable to start health checking server: no mgmt ip") + klog.Infof("Unable to start Egress IP health checking server: no mgmt ip") + return nil }
- depends on
-
OCPBUGS-4611 [4.13] Egress IP Health Check Is Not Compatible With VF (Hardware Backed) Management Port
- Closed
- is cloned by
-
OCPBUGS-4611 [4.13] Egress IP Health Check Is Not Compatible With VF (Hardware Backed) Management Port
- Closed
- links to