Hide Forgot
job: release-openshift-origin-installer-e2e-aws-sdn-network-stress-4.9 is permanently failing in CI: https://testgrid.k8s.io/redhat-openshift-ocp-release-4.9-informing#release-openshift-origin-installer-e2e-aws-sdn-network-stress-4.9 Example job: https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-sdn-network-stress-4.9/1412670635993206784
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