Job:
#TRT-1501issue7 weeks agoNetPol tests may not be recording results correctly? In Progress
Issue 15799618: NetPol tests may not be recording results correctly?
Description: On https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-gcp-ovn-upgrade-4.15-micro-release-openshift-release-analysis-aggregator/1756168710529224704 we failed three netpol tests on just one result, failure, with no successess. However the other 9 jobs seemed to run fine.
 
 [sig-network] Netpol NetworkPolicy between server and client should allow ingress access from namespace on one named port [Feature:NetworkPolicy] [Skipped:Network/OVNKubernetes] [Skipped:Network/OpenShiftSDN/Multitenant] [Skipped:Network/OpenShiftSDN] [Suite:openshift/conformance/parallel] [Suite:k8s]
 
 [sig-network] Netpol NetworkPolicy between server and client should allow egress access on one named port [Feature:NetworkPolicy] [Skipped:Network/OVNKubernetes] [Skipped:Network/OpenShiftSDN/Multitenant] [Skipped:Network/OpenShiftSDN] [Suite:openshift/conformance/parallel] [Suite:k8s]
 
 [sig-network] Netpol NetworkPolicy between server and client should allow ingress access on one named port [Feature:NetworkPolicy] [Skipped:Network/OVNKubernetes] [Skipped:Network/OpenShiftSDN/Multitenant] [Skipped:Network/OpenShiftSDN] [Suite:openshift/conformance/parallel] [Suite:k8s]
 
 Something seems funky with these tests, they're barely running, they don't seem to consistently report results. [4.15 has just 3 runs in the last two weeks|https://sippy.dptools.openshift.org/sippy-ng/tests/4.15/analysis?test=%5Bsig-network%5D%20Netpol%20NetworkPolicy%20between%20server%20and%20client%20should%20allow%20ingress%20access%20from%20namespace%20on%20one%20named%20port%20%5BFeature%3ANetworkPolicy%5D%20%5BSkipped%3ANetwork%2FOVNKubernetes%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%2FMultitenant%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D%20%5BSuite%3Ak8s%5D&filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22%5Bsig-network%5D%20Netpol%20NetworkPolicy%20between%20server%20and%20client%20should%20allow%20ingress%20access%20from%20namespace%20on%20one%20named%20port%20%5BFeature%3ANetworkPolicy%5D%20%5BSkipped%3ANetwork%2FOVNKubernetes%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%2FMultitenant%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D%20%5BSuite%3Ak8s%5D%22%7D%5D%2C%22linkOperator%22%3A%22and%22%7D], however [4.16 has just 1 but it passed|https://sippy.dptools.openshift.org/sippy-ng/tests/4.16/analysis?test=%5Bsig-network%5D%20Netpol%20NetworkPolicy%20between%20server%20and%20client%20should%20allow%20ingress%20access%20from%20namespace%20on%20one%20named%20port%20%5BFeature%3ANetworkPolicy%5D%20%5BSkipped%3ANetwork%2FOVNKubernetes%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%2FMultitenant%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D%20%5BSuite%3Ak8s%5D&filters=%7B%22items%22%3A%5B%7B%22columnField%22%3A%22name%22%2C%22operatorValue%22%3A%22equals%22%2C%22value%22%3A%22%5Bsig-network%5D%20Netpol%20NetworkPolicy%20between%20server%20and%20client%20should%20allow%20ingress%20access%20from%20namespace%20on%20one%20named%20port%20%5BFeature%3ANetworkPolicy%5D%20%5BSkipped%3ANetwork%2FOVNKubernetes%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%2FMultitenant%5D%20%5BSkipped%3ANetwork%2FOpenShiftSDN%5D%20%5BSuite%3Aopenshift%2Fconformance%2Fparallel%5D%20%5BSuite%3Ak8s%5D%22%7D%5D%2C%22linkOperator%22%3A%22and%22%7D]
 
 Whatever's going on, it's capable of taking out a payload, though it's not happening 100% of the time. https://amd64.ocp.releases.ci.openshift.org/releasestream/4.15.0-0.ci/release/4.15.0-0.ci-2024-02-10-040857
Status: In Progress
periodic-ci-openshift-release-master-ci-4.16-e2e-azure-ovn-upgrade (all) - 210 runs, 29% failed, 2% of failures match = 0% impact
#1780325333765984256junit12 days ago
# [sig-network] Netpol NetworkPolicy between server and client should enforce policy to allow ingress traffic from pods in all namespaces [Feature:NetworkPolicy] [Skipped:Network/OpenShiftSDN/Multitenant] [Suite:openshift/conformance/parallel] [Suite:k8s]
fail [k8s.io/kubernetes@v1.29.0/test/e2e/network/netpol/test_helper.go:129]: Had 8 wrong results in reachability matrix

Found in 0.48% of runs (1.64% of failures) across 210 total runs and 1 jobs (29.05% failed) in 1.256s - clear search | chart view - source code located on github