OCPBUGS-78978: Workaround packet sniffer timeouts in BGP tests

[jcaamano]

It's been observed that deployment of packet sniffer daemonset times out more frequently in BGP tests lately. This seems to be due to long image pull times. These have been frequently observed to be around the 4min mark:

I0330 07:19:42.759411 80700 dump.go:53] At 2026-03-30 07:18:33 +0000 UTC - event for e2e-test-bgp-n4x8l-packet-sniffer-bcmrq: {kubelet worker-1.ostest.test.metalkube.org} Pulled: Successfully pulled image "registry.ci.openshift.org/ocp/4.22-2026-03-29-160521@sha256:faa0dab4b09b21fe7cbe8735a22291565ea8119bf917425954ae0175365e2f43" in 4m4.352s (4m4.352s including waiting). Image size: 1731715382 bytes.

Align packet sniffer timeout to the typical 5 min timeout used elsewhere for pulling images. This does not intend to be a definitive solution but might improve things in the meantime.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[jcaamano]

/test ?

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Review skipped — only excluded labels are configured. (1)

• do-not-merge/work-in-progress

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: defbce6a-3a4c-4de6-9755-1108f72eebec

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jcaamano]

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw

[jcaamano]

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw

[openshift-ci-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[jcaamano]

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw

[arkadeepsen]

The packet sniffer daemonset issue is not showing up with the increased timeout. Retrying the test to check whether it flakes or not.

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw

[arkadeepsen]

The tests were flaking on this lane also.

/test e2e-metal-ipi-ovn-dualstack-bgp

[jcaamano]

@arkadeepsen sorry, updated the PR description with the intention of the change: #30912 (comment). Not intending for this to be a definitive fix, maybe just an improvement.

[arkadeepsen]

One last rerun

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw
/test e2e-metal-ipi-ovn-dualstack-bgp

[arkadeepsen]

/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw

[arkadeepsen]

In all the CI runs the packet sniffer daemonset pods are created successfully and the corresponding tests are passing.

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arkadeepsen, jcaamano

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• test/extended/networking/OWNERS [jcaamano]

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

[openshift-ci-robot]

@jcaamano: This pull request references Jira Issue OCPBUGS-78978, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

It's been observed that deployment of packet sniffer daemonset times out more frequently in BGP tests lately. This seems to be due to long image pull times. These have been frequently observed to be around the 4min mark:

I0330 07:19:42.759411 80700 dump.go:53] At 2026-03-30 07:18:33 +0000 UTC - event for e2e-test-bgp-n4x8l-packet-sniffer-bcmrq: {kubelet worker-1.ostest.test.metalkube.org} Pulled: Successfully pulled image "registry.ci.openshift.org/ocp/4.22-2026-03-29-160521@sha256:faa0dab4b09b21fe7cbe8735a22291565ea8119bf917425954ae0175365e2f43" in 4m4.352s (4m4.352s including waiting). Image size: 1731715382 bytes.

Align packet sniffer timeout to the typical 5 min timeout used elsewhere for pulling images. This does not intend to be a definitive solution but might improve things in the meantime.

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.

[jcaamano]

/verified-by CI

[jcaamano]

/verified by CI

[openshift-ci-robot]

@jcaamano: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

[jcaamano]

/jira refresh

[openshift-ci-robot]

@jcaamano: This pull request references Jira Issue OCPBUGS-78978, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

/jira refresh

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.

[jcaamano]

/jira refresh

[openshift-ci-robot]

@jcaamano: This pull request references Jira Issue OCPBUGS-78978, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Details

In response to this:

/jira refresh

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-robot]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-ci]

@jcaamano: 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-metal-ipi-ovn-dualstack-bgp	6263ffd	link	false	/test e2e-metal-ipi-ovn-dualstack-bgp
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-local-gw	6263ffd	link	false	/test e2e-metal-ipi-ovn-dualstack-bgp-local-gw

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-ci-robot]

@jcaamano: Jira Issue Verification Checks: Jira Issue OCPBUGS-78978
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-78978 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

It's been observed that deployment of packet sniffer daemonset times out more frequently in BGP tests lately. This seems to be due to long image pull times. These have been frequently observed to be around the 4min mark:

I0330 07:19:42.759411 80700 dump.go:53] At 2026-03-30 07:18:33 +0000 UTC - event for e2e-test-bgp-n4x8l-packet-sniffer-bcmrq: {kubelet worker-1.ostest.test.metalkube.org} Pulled: Successfully pulled image "registry.ci.openshift.org/ocp/4.22-2026-03-29-160521@sha256:faa0dab4b09b21fe7cbe8735a22291565ea8119bf917425954ae0175365e2f43" in 4m4.352s (4m4.352s including waiting). Image size: 1731715382 bytes.

Align packet sniffer timeout to the typical 5 min timeout used elsewhere for pulling images. This does not intend to be a definitive solution but might improve things in the meantime.

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-merge-robot]

Fix included in accepted release 4.22.0-0.nightly-2026-04-01-092906