flake: [FAIL] e2e egress IP validation [OVN network] Using different methods to disable a node's availability for egress Should validate the egress IP functionality against remote hosts [It] disabling egress nodes impeding GRCP health check

jcaamano commented 7 months ago

Saw in PR with no functional changes https://github.com/ovn-org/ovn-kubernetes/actions/runs/7828991661/job/21360775911

tssurya commented 7 months ago

saw this again: https://github.com/ovn-org/ovn-kubernetes/pull/4159#issuecomment-1964463029

kyrtapz commented 6 months ago

saw this here: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8253752596/job/22577354962?pr=4216

kyrtapz commented 6 months ago

https://github.com/ovn-org/ovn-kubernetes/actions/runs/8263081969/job/22604714071?pr=4210

tssurya commented 6 months ago

hit this again: https://github.com/ovn-org/ovn-kubernetes/pull/4164#issuecomment-2024103599

trozet commented 6 months ago

hit again: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8452396435/job/23153838483?pr=4243

jcaamano commented 6 months ago

I am re-wroking the healthcheck thingy which can potentially take care of this.

flavio-fernandes commented 6 months ago

hit this again: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8511378093/job/23311649085?pr=4103

tssurya commented 6 months ago

hitting again https://github.com/ovn-org/ovn-kubernetes/pull/4240#issuecomment-2031613457 assigning this to Jaime based on his previous comment (please unassign yourself if I did the wrong choice here; and we can assign it d/s with the bugs to someone else)

pperiyasamy commented 6 months ago

hit this again: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8535389443/job/23382774461?pr=4240. Please ignore if its redundant.

tssurya commented 6 months ago

again: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8546598998/job/23417934597?pr=4248

flavio-fernandes commented 6 months ago

again: https://github.com/ovn-org/ovn-kubernetes/actions/runs/8562504808/job/23466444668?pr=4103

trozet commented 5 months ago

from #4103 logs I see:

I0405 00:49:46.865868      52 egressip_controller.go:1341] Successful assignment of egress IP: 172.18.1.5 to network 172.18.0.0/16 on node: &{egressIPConfig:0xc000679380 mgmtIPs:[[10 128 0 2]] allocations:map[172.18.1.4:egressip 172.18.1.5:egressip-2] healthClient:0xc0007534a0 isReady:true isReachable:true isEgressAssignable:true name:ovn-worker2}
I0405 00:49:46.865904      52 egressip_controller.go:133] Patching status on EgressIP egressip-2: [{ovn-worker2 172.18.1.5}]
W0405 00:49:46.870790      52 egressip.go:575] EgressIP object egressip will not be configured for pod egressip-8050_e2e-egressip-pod-1 since another egressIP object egressip-2 is serving it
W0405 00:49:46.870790      52 egressip.go:575] EgressIP object egressip will not be configured for pod egressip-8050_e2e-egressip-pod-1 since another egressIP object egressip-2 is serving it
I0405 00:49:46.871192      52 event.go:364] Event(v1.ObjectReference{Kind:"EgressIP", Namespace:"", Name:"egressip", UID:"", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Warning' reason: 'UndefinedRequest' EgressIP object egressip will not be configured for pod egressip-8050_e2e-egressip-pod-1 since another egressIP object egressip-2 is serving it, this is undefined

flavio-fernandes commented 3 months ago

again: https://github.com/ovn-org/ovn-kubernetes/actions/runs/9414617767/job/25934979357?pr=4413