https://bugzilla.redhat.com/show_bug.cgi?id=1989169 is filed to re-enable the following test cases which fail: - [sig-network-edge][Feature:Idling] Unidling should work with TCP (when fully idled) - [sig-network-edge][Feature:Idling] Unidling should work with TCP (while idling) This bz is to track the work to fix the bug in ovn-kube that causes the failures. Once the failures are resolved, this PR will re-enable the tests in CI: https://github.com/openshift/origin/pull/26460
just fyi that the PR to re-enable these tests does have an example of one failure: https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/26460/pull-ci-openshift-origin-master-e2e-aws-ovn/1440695779755823104
'Unidling should work with TCP' issue is seen on OCP 4.10 RC2 build as well. # oc version Client Version: 4.10.0-rc.2 Server Version: 4.10.0-rc.2 Kubernetes Version: v1.23.3+2e8bad7 # oc get network.config/cluster -o jsonpath='{.status.networkType}{"\n"}' OVNKubernetes The attached file "Test failure logs seen with ocp410 RC 2 build.txt" has the entire log seen for test : [sig-network-edge][Feature:Idling] Unidling should work with TCP (when fully idled) [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel] Test failure log file link https://drive.google.com/file/d/1iejCCgL6q6qttq4icCRi1TMsC_s-8fVc/view?usp=sharing Some more tests which fail are : [sig-network] Services should have session affinity timeout work for NodePort service [LinuxOnly] [Conformance] [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] [sig-network] Services should have session affinity timeout work for service with type clusterIP [LinuxOnly] [Conformance] [Skipped:Network/OVNKubernetes] [Suite:openshift/conformance/parallel/minimal] [Suite:k8s] The below file has must has must gather logs seen for cluster : https://drive.google.com/file/d/1JjF3JtAU4bNHuYHNAvJwnk5mzZE1yKQS/view?usp=sharing
e2e failure was also observed with "release-ppc64le:4.9.0-0.nightly-ppc64le-2022-04-12-205337"
Unidling should work with TCP' issue is seen on OCP 4.9.33 build as well. # oc version Client Version: 4.9.32 Server Version: 4.9.33 Kubernetes Version: v1.22.8+c02bd9d # oc get network.config/cluster -o jsonpath='{.status.networkType}{"\n"}' OpenShiftSDN Test failure log file link: https://drive.google.com/file/d/1NQjt3JI6iOrafbiUwTtq0FO5Uw10YDIu/view?usp=sharing The below file has must has must gather logs seen for cluster : https://drive.google.com/file/d/1jhr9RHf2o04ChgbdcwruBuvEwNUCHYa7/view?usp=sharing
@sbiragda Thanks for that note, I'd filed https://bugzilla.redhat.com/show_bug.cgi?id=2085327 observing the issue in 4.9 nightly and ci builds.
*** Bug 2077167 has been marked as a duplicate of this bug. ***
*** Bug 2085327 has been marked as a duplicate of this bug. ***
OCP is no longer using Bugzilla and this bug appears to have been left in an orphaned state. If the bug is still relevant, please open a new issue in the OCPBUGS Jira project: https://issues.redhat.com/projects/OCPBUGS/summary
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days