Bug 1979962
Summary: | AWS SDN Network Stress tests have not passed in 4.9 release-openshift-origin-installer-e2e-aws-sdn-network-stress-4.9 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Stephen Benjamin <stbenjam> |
Component: | Networking | Assignee: | Nadia Pinaeva <npinaeva> |
Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | medium | ||
Priority: | medium | CC: | anusaxen, sippy |
Version: | 4.9 | ||
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: | Environment: |
job=periodic-ci-openshift-release-master-ci-4.9-e2e-aws-network-stress=all
|
|
Last Closed: | 2022-03-12 04:35:46 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: |
Description
Stephen Benjamin
2021-07-07 13:59:14 UTC
Seems like the job was removed from release-4.9-periodics (https://github.com/openshift/release/commit/b6efa2e82507bc00b9406bd55cfb5c468d5cca29) The commit you linked is Clayton moving to a generated job, it’s still present. It’s now called e2e-aws-network-stress. The last run failed: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-aws-network-stress/1414651685946527744 Of course, I saw that it's present, I was just curious why the job was moved and if it changes something from your perspective. Since Clayton increased container memory limits, the job Passed (https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/periodic-ci-openshift-release-master-ci-4.9-e2e-aws-network-stress/1415704490236973056). We may wait for the next run in two days and see if success is permanent. 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 |