Bug 2000754
| Summary: | IPerf2 tests should be lower | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Stephen Benjamin <stbenjam> | |
| Component: | Installer | Assignee: | Pierre Prinetti <pprinett> | |
| Installer sub component: | OpenShift on OpenStack | QA Contact: | Jon Uriarte <juriarte> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | medium | |||
| Priority: | medium | CC: | m.andre, mbooth, pprinett, sippy | |
| Version: | 4.9 | Keywords: | Reopened | |
| 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: | ||||
| : | 2010225 (view as bug list) | Environment: |
job=periodic-ci-openshift-release-master-ci-4.9-e2e-openstack-parallel=all
job=release-openshift-ocp-installer-e2e-aws-upi-4.10=all
job=release-openshift-ocp-installer-e2e-aws-upi-4.9=all
job=release-openshift-origin-installer-old-rhcos-e2e-aws-4.10=all
[sig-network] Networking IPerf2 [Feature:Networking-Performance] should run iperf2
|
|
| Last Closed: | 2022-03-10 16:07:01 UTC | Type: | Bug | |
| 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: | 2010225 | |||
|
Description
Stephen Benjamin
2021-09-02 19:55:14 UTC
It seems like these jobs would have otherwise passed if the Iperf2 job was not running. We don't care to test the networking performance of our CI hardware anyway, so we are moving to skip this test. Backport to kubernetes 1.22 The upstream fix has been backported to 1.22, but has not yet been included in a tagged release. The most recent tag was 1.22.1, so we can expect the fix to be included in 1.22.2. I believe the path to resolving this bug is: 1. Commit a0bebe70ef268e097d775a8e76a725e81a548fad is included in upstream tag 1.22.2 2. openshift/kubernetes:master rebases on upstream tag 1.22.2 3. openshift/origin revendors k8s.io/kubernetes on openshift/kubernetes:master Ideally all of these things should happen automatically over the next few weeks. *** Bug 2006346 has been marked as a duplicate of this bug. *** > Ideally all of these things should happen automatically over the next few weeks. This is failing quite a bit, not on just the openstack job -- can we bring the fix from upstream directly? https://github.com/openshift/kubernetes/pull/980 Even though the openshift/kubernetes change merged 2 days ago, we're still seeing issues in our CI: https://prow.ci.openshift.org/view/gcs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.10-e2e-openstack-parallel/1443518614392016896 I assume it needs to be re-vendored in openshift/origin now? Looks fine, I am not seeing new runs failed because of iPerf2 for now. Moving back to ON_QA as we need to move the bug to VERIFIED in order for the backport to be valid. Self-verifying. This iperf2 test is no longer an issue on 4.10 as shown by: https://search.ci.openshift.org/?search=should+run+iperf2&maxAge=48h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job Removing the Triaged keyword because: * the QE automation assessment (flag qe_test_coverage) is missing 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 |