[release-4.19] CORENET-5668: Update IPsec e2e test to validate NAT-T encapsulation option #29944
Conversation
Signed-off-by: Periyasamy Palanisamy <[email protected]>
This commit adds required tests to ensure pod traffic across nodes are not impacted upon multiple reboot of ipsec dameonset pods. Signed-off-by: Periyasamy Palanisamy <[email protected]>
|
@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CORENET-5668 In response to this:
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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: openshift-cherrypick-robot The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/test e2e-aws-ovn-serial-ipsec |
|
/assign @martinkennelly @dgoodwin |
|
/test e2e-aws-ovn-serial-ipsec |
|
/retest-required |
|
/test e2e-aws-ovn-serial-ipsec |
|
/retest-required |
|
somehow ipsec resilence tests are failing with the run https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29944/pull-ci-openshift-origin-release-4.19-e2e-aws-ovn-serial-ipsec/1940717261111169024, it's not able to get ipsec-webserver daemonset pods up and running. need to troublehshoot E2E. |
Logs doesn't provide enough info why all ipsec-webserver pods not in available state (since those pods are also deleted as part of test teardown). can not reproduce the issue locally on a bot cluster, trying to run the test few more times to see if it's reproducible again. |
|
/test e2e-aws-ovn-serial-ipsec |
|
@openshift-cherrypick-robot: The following tests failed, say
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-sigs/prow repository. I understand the commands that are listed here. |
|
/close in favor of #29957. it also fixes mentioned issue #29944 (comment). |
|
@pperiyasamy: Closed this PR. In response to this:
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-sigs/prow repository. |
5 participants
This is an automated cherry-pick of #29563
/assign pperiyasamy