-
Bug
-
Resolution: Cannot Reproduce
-
Major
-
None
-
4.16.0
-
Important
-
No
-
SDN Sprint 255
-
1
-
Rejected
-
False
-
Original: Description of problem:
on IBM powervs cluster, Egress IP Health Server is not started in ovnkube-node pods in ovnkube-controller containers for master nodes
Version-Release number of selected component (if applicable):
4.16.0-ec.4
How reproducible:
Steps to Reproduce:
1. on IBM powervs provided by power team, check in ovnkube-controller pod of each ovnkube-node pod to see if Egress IP health monitoring over GRPC has been started 2. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-ec.4 True False 20d Cluster version is 4.16.0-ec.4 $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-ec.4 True False 20d Cluster version is 4.16.0-ec.4 $ oc -n openshift-ovn-kubernetes -c ovnkube-controller logs ovnkube-node-9zq7s | grep "Health " W0418 10:05:57.154322 4231 egressip_healthcheck.go:71] Health checking using insecure connection I0418 10:05:57.154526 4231 egressip_healthcheck.go:87] Starting Egress IP Health Server on 10.128.2.2:9107 $ $ $ oc -n openshift-ovn-kubernetes -c ovnkube-controller logs ovnkube-node-dvc6h | grep "Health " W0418 10:11:12.289779 4235 egressip_healthcheck.go:71] Health checking using insecure connection I0418 10:11:12.289847 4235 egressip_healthcheck.go:87] Starting Egress IP Health Server on 10.129.2.2:9107 $ $ $ $ oc -n openshift-ovn-kubernetes -c ovnkube-controller logs ovnkube-node-lpvqw | grep "Health " W0427 02:32:48.813157 4033 egressip_healthcheck.go:71] Health checking using insecure connection I0427 02:32:48.813213 4033 egressip_healthcheck.go:87] Starting Egress IP Health Server on 10.131.0.2:9107 $ $ $ oc -n openshift-ovn-kubernetes -c ovnkube-controller logs ovnkube-node-pg8d6 | grep "Health " $ $ oc -n openshift-ovn-kubernetes -c ovnkube-controller logs ovnkube-node-sdpmm | grep "Health " $ $ oc -n openshift-ovn-kubernetes -c ovnkube-controller logs ovnkube-node-vw9jl | grep "Health " $ 3.
Actual results:
EIP health monitoring server is only started on worker nodes
Expected results:
EIP health monitoring server should be started on all nodes like all other platforms
Additional info: