Skip to content

[release-4.18] SDN-4168: Optimize timing for IPsec tests - #29411

Closed
openshift-cherrypick-robot wants to merge 3 commits into
openshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-28797-to-release-4.18
Closed

[release-4.18] SDN-4168: Optimize timing for IPsec tests #29411
openshift-cherrypick-robot wants to merge 3 commits into
openshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-28797-to-release-4.18

Conversation

@openshift-cherrypick-robot

Copy link
Copy Markdown

This is an automated cherry-pick of #28797

/assign jluhrsen

The ipsec test suite takes about 5-6 hours to finish running the tests
for e2e-aws-ovn-ipsec-serial CI lane, Hence this commit optimizes ipsec
tests so that it doesn't cause much of node reboots when changing ipsec
modes.

Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
This attempts to fix following error seen from ipsec test run:

I1118 11:08:34.394429 461 delete.go:70] Wait up to 5m0s for pod "ipsec-tcpdump-hostpod-vftlk" to be fully deleted
I1118 11:09:07.535653 461 exec_util.go:59] ExecWithOptions {Command:[/bin/sh -c cat /release-manifests/image-references] Namespace:e2e-test-ipsec-48sdq PodName:extract-release-imagerefs ContainerName:imagerefs Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:false Quiet:false}
I1118 11:09:07.536406 461 exec_util.go:66] ExecWithOptions: Clientset creation
I1118 11:09:07.536456 461 exec_util.go:83] ExecWithOptions: execute(POST https://api.ci-op-6ic49xd0-f3b46.aws-2.ci.openshift.org:6443/api/v1/namespaces/e2e-test-ipsec-48sdq/pods/extract-release-imagerefs/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Frelease-manifests%2Fimage-references&container=imagerefs&container=imagerefs&stderr=true&stdout=true)
I1118 11:09:07.642284 461 exec_util.go:111] Exec stderr: ""
I1118 11:09:07.642418 461 exec_util.go:112] Unexpected error: failed to execute command in pod extract-release-imagerefs, container imagerefs: error sending request: Post "https://api.ci-op-6ic49xd0-f3b46.aws-2.ci.openshift.org:6443/api/v1/namespaces/e2e-test-ipsec-48sdq/pods/extract-release-imagerefs/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Frelease-manifests%2Fimage-references&container=imagerefs&container=imagerefs&stderr=true&stdout=true": read tcp 10.131.68.7:51092->54.244.16.237:6443: read: connection reset by peer:
     <*errors.errorString | 0xc006aabf10>:
      error sending request: Post "https://api.ci-op-6ic49xd0-f3b46.aws-2.ci.openshift.org:6443/api/v1/namespaces/e2e-test-ipsec-48sdq/pods/extract-release-imagerefs/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Frelease-manifests%2Fimage-references&container=imagerefs&container=imagerefs&stderr=true&stdout=true": read tcp 10.131.68.7:51092->54.244.16.237:6443: read: connection reset by peer
      {
          s: "error sending request: Post \"https://api.ci-op-6ic49xd0-f3b46.aws-2.ci.openshift.org:6443/api/v1/namespaces/e2e-test-ipsec-48sdq/pods/extract-release-imagerefs/exec?command=%2Fbin%2Fsh&command=-c&command=cat+%2Frelease-manifests%2Fimage-references&container=imagerefs&container=imagerefs&stderr=true&stdout=true\": read tcp 10.131.68.7:51092->54.244.16.237:6443: read: connection reset by peer",
      }
    [FAILED] in [It] - k8s.io/kubernetes@v1.31.1/test/e2e/framework/pod/exec_util.go:112 @ 11/18/24 11:09:07.701

Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
@openshift-ci-robot

openshift-ci-robot commented Jan 9, 2025

Copy link
Copy Markdown

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SDN-4168

Details

In response to this:

This is an automated cherry-pick of #28797

/assign jluhrsen

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.

@openshift-ci
openshift-ci Bot requested review from beekhof and sjenning January 9, 2025 02:54
@openshift-ci

openshift-ci Bot commented Jan 9, 2025

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
Once this PR has been reviewed and has the lgtm label, please assign stbenjam for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci

openshift-ci Bot commented Jan 9, 2025

Copy link
Copy Markdown
Contributor

@openshift-cherrypick-robot: 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-ovn-serial 0f308a1 link true /test e2e-aws-ovn-serial
ci/prow/e2e-gcp-csi 0f308a1 link false /test e2e-gcp-csi
ci/prow/e2e-gcp-ovn 0f308a1 link true /test e2e-gcp-ovn
ci/prow/e2e-agnostic-ovn-cmd 0f308a1 link false /test e2e-agnostic-ovn-cmd
ci/prow/e2e-aws-ovn-single-node-upgrade 0f308a1 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node 0f308a1 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-cgroupsv2 0f308a1 link false /test e2e-aws-ovn-cgroupsv2

Full PR test history. Your PR dashboard.

Details

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.

@openshift-bot

Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 9, 2025
@openshift-bot

Copy link
Copy Markdown
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 10, 2025
@openshift-bot

Copy link
Copy Markdown
Contributor

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

@openshift-ci openshift-ci Bot closed this Jun 9, 2025
@openshift-ci

openshift-ci Bot commented Jun 9, 2025

Copy link
Copy Markdown
Contributor

@openshift-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants