Bug 2098053: Re-revert "Add networking test for invalid external gateway"
Re-revert of https://github.com/openshift/origin/pull/26985 and fix the test for pod security level, ipv6 or dual stack clusters.
Signed-off-by: Periyasamy Palanisamy [email protected]
@pperiyasamy: This pull request references Bugzilla bug 2098053, which is invalid:
- expected the bug to target the "4.12.0" release, but it targets "4.11.0" instead
Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.
In response to this:
Bug 2098053: Re-revert "Add networking test for invalid external gateway"
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
@pperiyasamy: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.
In response to this:
Re-revert "Add networking test for invalid external gateway"
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/assign @stbenjam @trozet
/retest
@pperiyasamy: This pull request references Bugzilla bug 2098053, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.
3 validation(s) were run on this bug
- bug is open, matching expected state (open)
- bug target release (4.12.0) matches configured target release for branch (4.12.0)
- bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
Requesting review from QA contact: /cc @anuragthehatter
In response to this:
Bug 2098053: Re-revert "Add networking test for invalid external gateway"
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
/retest
/test all
/retest
/retest
/retest
/retest
/retest
@pperiyasamy: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/e2e-aws-single-node-upgrade | 9f96b612c29856a3666f0d8e185f8a208c225719 | link | false | /test e2e-aws-single-node-upgrade |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.
/lgtm /approve
/assign @stbenjam
/approve
Sorry for delay.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: dcbw, pperiyasamy, stbenjam
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~test/extended/networking/OWNERS~~ [dcbw,stbenjam]
- ~~test/extended/util/annotate/generated/OWNERS~~ [stbenjam]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/retest-required
Remaining retests: 2 against base HEAD d30568b36280c96fe15fa46e9769e888069e00bf and 8 for PR HEAD 9f96b612c29856a3666f0d8e185f8a208c225719 in total
/retest-required
Remaining retests: 1 against base HEAD d30568b36280c96fe15fa46e9769e888069e00bf and 7 for PR HEAD 9f96b612c29856a3666f0d8e185f8a208c225719 in total
@pperiyasamy: All pull requests linked via external trackers have merged:
Bugzilla bug 2098053 has been moved to the MODIFIED state.
In response to this:
Bug 2098053: Re-revert "Add networking test for invalid external gateway"
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.