Bug 2017036

Summary: [sig-network-edge][Feature:Idling] Unidling should handle many TCP connections fails in periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn
Product: OpenShift Container Platform Reporter: Matthew Booth <mbooth>
Component: InstallerAssignee: Matthew Booth <mbooth>
Installer sub component: OpenShift on OpenStack QA Contact: Jon Uriarte <juriarte>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: medium CC: aos-bugs, emacchi, juriarte, pprinett, sippy, stephenfin
Version: 4.9Keywords: Reopened, Triaged
Target Milestone: ---   
Target Release: 4.10.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: 1989100 Environment:
job=periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn=all
Last Closed: 2022-03-10 16:21:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1989100    

Description Matthew Booth 2021-10-25 13:21:21 UTC
+++ This bug was initially created as a clone of Bug #1989100 +++

job:
periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn 

is failing frequently in CI, see testgrid results:
https://testgrid.k8s.io/redhat-openshift-ocp-release-4.9-informing#periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn

Here is a test run that had 8 errors only: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-ovn/1421446191245168640

In particular, these two tests seem to be failing most of the time:

* [sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2 [Suite:openshift/conformance/parallel] [Suite:k8s]
* [sig-auth][Feature:OpenShiftAuthorization][Serial] authorization TestAuthorizationResourceAccessReview should succeed [Suite:openshift/conformance/serial]

--- Additional comment from Pierre Prinetti on 2021-10-20 16:46:12 BST ---

From the bug triage meeting: we unset TRIAGED so that the pre-triager can assess the state of the periodic and update the status here.

--- Additional comment from Matthew Booth on 2021-10-25 14:16:03 BST ---

There are 3 tests which are failing 100% of the time:

openshift-tests.[sig-auth][Feature:OpenShiftAuthorization][Serial] authorization TestAuthorizationResourceAccessReview should succeed [Suite:openshift/conformance/serial]
openshift-tests.[sig-network-edge][Feature:Idling] Unidling should handle many TCP connections by possibly dropping those over a certain bound [Serial] [Suite:openshift/conformance/serial]
openshift-tests.[sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2 [Suite:openshift/conformance/parallel] [Suite:k8s]

Comment 1 Matthew Booth 2021-10-25 14:01:24 UTC
This is now being skipped, and already has a separate bug.

*** This bug has been marked as a duplicate of bug 1989169 ***

Comment 2 Matthew Booth 2021-10-25 14:47:11 UTC
This is not skipped and appears to be still broken.

Comment 3 Matthew Booth 2021-10-25 15:52:10 UTC
It appears that this isn't an OpenStack specific issue, so I investigated the equivalent AWS job, where is isn't failing because it isn't running. Crucially, AWS is running the default conformance test suite, openshift/conformance/parallel, where as OpenStack is running openshift/conformance, which includes both /parallel and /serial. The failing test is in /serial.

I don't believe we should be running /serial in this context. I'm going to submit a patch to make the OpenStack job identical to the AWS job.

Comment 4 Matthew Booth 2021-10-26 08:25:35 UTC
*** Bug 2017037 has been marked as a duplicate of this bug. ***

Comment 6 ShiftStack Bugwatcher 2021-11-25 16:12:50 UTC
Removing the Triaged keyword because:
* the priority assessment is missing

* the QE automation assessment (flag qe_test_coverage) is missing

Comment 11 errata-xmlrpc 2022-03-10 16:21:40 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056