Bug 2072171 - Test "[sig-network][Feature:EgressFirewall] EgressFirewall should have no impact outside its namespace [Suite:openshift/conformance/parallel]" fails
Summary: Test "[sig-network][Feature:EgressFirewall] EgressFirewall should have no imp...
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.11
Hardware: All
OS: Linux
Target Milestone: ---
: 4.11.0
Assignee: Mohamed Mahmoud
QA Contact: Anurag saxena
Depends On:
TreeView+ depends on / blocked
Reported: 2022-04-05 17:57 UTC by Dennis Periquet
Modified: 2022-08-10 11:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 11:03:38 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift origin pull 26973 0 None open Bug 2072171: Reenable the implementation for basic egressfw e2e CI test 2022-04-07 11:57:37 UTC

Description Dennis Periquet 2022-04-05 17:57:48 UTC
Description of problem:

The [sig-network][Feature:EgressFirewall] EgressFirewall should have no impact outside its namespace [Suite:openshift/conformance/parallel] test is failing so we had to revert it with https://github.com/openshift/origin/pull/26967

This BZ is to track the work to get that test back into CI using a revert PR for the PR mentioned above.  The criteria is also in the PR comment:

To unrevert this PR:

Run /payload 4.11 nightly informing three times.
For each attempt, check job/periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-proxy ; your test ([sig-network][Feature:EgressFirewall] EgressFirewall should have no impact outside its namespace [Suite:openshift/conformance/parallel]) must pass all three times.
Version-Release number of selected component (if applicable):

How reproducible: 
The PR shows a list of tests where the failure was noticed.  One in particular is in periodic-ci-openshift-release-master-nightly-4.11-e2e-aws-proxy; others include the arm64 tests.

Steps to Reproduce:
1.  See steps in the original PR (https://github.com/openshift/origin/pull/26934)

Actual results:

You can see the results using this like https://search.ci.openshift.org/?search=EgressFirewall+should+have+no+impact+outside+its+namespace&maxAge=48h&context=1&type=bug%2Bjunit&name=&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job and clicking on a job to see the test run failures and logs.  Search for a failing test with "EgressFirewall should have no impact outside its namespace" in the name.

Expected results:

The tests should pass.

Additional info:

Comment 4 errata-xmlrpc 2022-08-10 11:03:38 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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.


Note You need to log in before you can comment on or make changes to this bug.