You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summarizing 3 Failures:
[FAIL] OVS CPU affinity pinning [It] can be enabled on specific nodes by creating enable_dynamic_cpu_affinity file
/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/ovspinning.go:24
[FAIL] e2e ingress to host-networked pods traffic validation Validating ingress traffic to Host Networked pods with externalTrafficPolicy=local [It] Should be allowed to node local host-networked endpoints by nodeport services
/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/e2e.go:1773
[FAIL] Services of type NodePort [It] should listen on each host addresses
/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/service.go:734
Ran 57 of 251 Specs in 1785.912 seconds
FAIL! -- 54 Passed | 3 Failed | 1 Flaked | 0 Pending | 194 Skipped
2024-02-06T12:50:03.8766151Z �[1mSTEP:�[0m Destroying namespace "inter-node-e2e-9485" for this suite. �[38;5;243m@ 02/06/24 12:50:03.876�[0m
2024-02-06T12:50:03.8793512Z �[38;5;10m↺ [FLAKEY TEST - TOOK 2 ATTEMPTS TO PASS] [337.162 seconds]�[0m
2024-02-06T12:50:03.8795155Z �[38;5;243m------------------------------�[0m
2024-02-06T12:50:03.8812723Z �[0mOVS CPU affinity pinning �[0m�[1mcan be enabled on specific nodes by creating enable_dynamic_cpu_affinity file�[0m
2024-02-06T12:50:03.8814570Z �[38;5;243m/home/runner/work/ovn-kubernetes/ovn-kubernetes/test/e2e/ovspinning.go:12�[0m
2024-02-06T12:50:03.8815774Z �[1mSTEP:�[0m Creating a kubernetes client �[38;5;243m@ 02/06/24 12:50:03.879�[0m
2024-02-06T12:50:03.8816493Z Feb 6 12:50:03.879: INFO: >>> kubeConfig: /home/runner/ovn.conf
2024-02-06T12:50:03.8817413Z �[1mSTEP:�[0m Building a namespace api object, basename ovspinning �[38;5;243m@ 02/06/24 12:50:03.88�[0m
2024-02-06T12:50:03.8866687Z Feb 6 12:50:03.884: INFO: Skipping waiting for service account
2024-02-06T12:50:03.9389235Z Feb 6 12:50:03.938: INFO: restarting ovnkube-node for [ovn-worker ovn-worker2]
2024-02-06T12:50:03.9438782Z Feb 6 12:50:03.943: INFO: Deleting pod "ovnkube-node-fwnxm" in namespace "ovn-kubernetes"
2024-02-06T12:50:03.9440600Z Feb 6 12:50:03.943: INFO: Deleting pod "ovnkube-node-2c47f" in namespace "ovn-kubernetes"
2024-02-06T12:50:03.9488669Z Feb 6 12:50:03.948: INFO: Wait up to 5m0s for pod "ovnkube-node-2c47f" to be fully deleted
2024-02-06T12:50:03.9749902Z Feb 6 12:50:03.974: INFO: Wait up to 5m0s for pod "ovnkube-node-fwnxm" to be fully deleted
2024-02-06T12:50:14.0227116Z Feb 6 12:50:14.022: INFO: waiting for node ovn-worker2 to have running ovnkube-node pod
Goal; Fix this and re-enable this test back in the CP lanes. Now they are skipped as part of #4106 for IPV6
The text was updated successfully, but these errors were encountered:
This one is weird actually because this doesn't always fail!
only fails on LGW+IPV6:
https://github.com/ovn-org/ovn-kubernetes/actions/runs/7799278970/job/21270728006?pr=4106
but it Flaked in SGW and passed the second time :D
https://github.com/ovn-org/ovn-kubernetes/actions/runs/7799278970/job/21270728558?pr=4106
Goal; Fix this and re-enable this test back in the CP lanes. Now they are skipped as part of #4106 for IPV6
The text was updated successfully, but these errors were encountered: