origin
origin copied to clipboard
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
Run sendEgressIPProbesAndCheckPacketSnifferLogs until it eventually succeeds of for a maximum of 2 minutes. Before, we checked first until a single packet was EgressIP mapped, and then ran the main test once. Instead, simply make sure that the test eventually passed to cut down on flakes.
Signed-off-by: Andreas Karis [email protected]
How to test with SDN:
./openshift-tests run all --print-commands | grep EgressIP | grep external | grep -v "Skipped:Network/OpenShiftSDN" | while IFS= read -r line; do bash -c "$line" ; done
How to test with OVN:
./openshift-tests run all --print-commands | grep EgressIP | grep external | grep -v "Skipped:Network/OVNKubernetes" | while IFS= read -r line; do bash -c "$line" ; done
Tested manually with:
- SDN + AWS (latest)
- OVN Azure (4.10)
- OVN + AWS (latest)
@andreaskaris: This pull request references Bugzilla bug 2110503. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state. Warning: Failed to comment on Bugzilla bug with reason for changed state.
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, 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 NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, 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 NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, which is valid.
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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, which is valid.
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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, which is valid.
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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, which is valid.
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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.
@andreaskaris: This pull request references Bugzilla bug 2110503, which is valid.
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 POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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-required
/lgtm
/retest
/retest
/retest
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: andreaskaris, jluhrsen, 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~~ [stbenjam]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@andreaskaris: The following tests 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 | fa1667da0994040190b3f555e2145be92f46d993 | link | false | /test e2e-aws-single-node |
| ci/prow/e2e-aws-single-node-upgrade | fa1667da0994040190b3f555e2145be92f46d993 | 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.
@andreaskaris: All pull requests linked via external trackers have merged:
Bugzilla bug 2110503 has been moved to the MODIFIED state.
In response to this:
Bug 2110503: EgressIP: Probes and check tcpdump logs should succeed eventually
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.