OCPBUGS-83286: Fix case-sensitive error matching in Whereabouts IP allocation test by pperiyasamy · Pull Request #31012 · openshift/origin

pperiyasamy · 2026-04-15T09:30:51Z

Update the test to match the exact error string returned by the cmd add operation.

Reference:
https://github.com/openshift/whereabouts-cni/blob/release-4.22/cmd/whereabouts.go#L90

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network 
{  5 failures to create the sandbox
...
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-rn69f node/ci-op-s9md65n3-5bc1c-lsqlc-worker-eastus2-pdd8k pod/whereabouts-pod-cb6ld hmsg/32f45005d9 - race condition: sandbox failure at pod creation time (new pod created -34.35 seconds after deletion started) - firstTimestamp/2026-04-12T16:43:23Z interesting/true lastTimestamp/2026-04-12T16:43:23Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-cb6ld_e2e-test-whereabouts-e2e-rn69f_784dd26c-4e4d-4f92-90e9-ef57502c9845_0(1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99): error adding pod e2e-test-whereabouts-e2e-rn69f_whereabouts-pod-cb6ld to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99" Netns:"/var/run/netns/43532160-5396-417e-8cb3-221c162a04d8" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-rn69f;K8S_POD_NAME=whereabouts-pod-cb6ld;K8S_POD_INFRA_CONTAINER_ID=1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99;K8S_POD_UID=784dd26c-4e4d-4f92-90e9-ef57502c9845" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld] networking: [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld/784dd26c-4e4d-4f92-90e9-ef57502c9845:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-rn69f node/ci-op-s9md65n3-5bc1c-lsqlc-worker-eastus2-pdd8k pod/whereabouts-pod-cb6ld hmsg/f2578ad644 - race condition: sandbox failure at pod creation time (new pod created -30.35 seconds after deletion started) - firstTimestamp/2026-04-12T16:43:27Z interesting/true lastTimestamp/2026-04-12T16:43:27Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-cb6ld_e2e-test-whereabouts-e2e-rn69f_784dd26c-4e4d-4f92-90e9-ef57502c9845_0(920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae): error adding pod e2e-test-whereabouts-e2e-rn69f_whereabouts-pod-cb6ld to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae" Netns:"/var/run/netns/dd8abd81-1fbf-448e-97a8-2a580559ec28" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-rn69f;K8S_POD_NAME=whereabouts-pod-cb6ld;K8S_POD_INFRA_CONTAINER_ID=920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae;K8S_POD_UID=784dd26c-4e4d-4f92-90e9-ef57502c9845" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld] networking: [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld/784dd26c-4e4d-4f92-90e9-ef57502c9845:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]

'
'

Summary by CodeRabbit

Tests
- Improved network testing to more reliably detect IP-range exhaustion errors during pod sandbox creation, enhancing test accuracy and reliability.

Update the test to match the exact error string returned by the cmd add operation. Reference: https://github.com/openshift/whereabouts-cni/blob/release-4.22/cmd/whereabouts.go#L90 Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>

openshift-merge-bot · 2026-04-15T09:30:54Z

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

coderabbitai · 2026-04-15T09:32:15Z

Walkthrough

A test condition in the network monitor tests was adjusted to match error messages with different capitalization. The substring filter for whereabouts IP allocation failures was changed from "Error" to "error" at the beginning of the error message to accommodate case variations in error output.

Changes

Cohort / File(s)	Summary
Error Message Matching `pkg/monitortests/network/legacynetworkmonitortests/networking.go`	Modified the error substring filter in `testPodSandboxCreation` from `"Error at storage engine..."` to `"error at storage engine..."` to handle lowercase error message variants. This adjustment determines which IP-range exhaustion failures are treated as expected rather than failures.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 8 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Ipv6 And Disconnected Network Test Compatibility	❓ Inconclusive	Unable to locate or examine the modified networking.go file in the PR to verify for IPv4-only assumptions or external connectivity requirements in new Ginkgo e2e tests.	Please provide the actual PR changes or file path to analyze the test modifications for IPv4 assumptions and external connectivity dependencies.

✅ Passed checks (8 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Stable And Deterministic Test Names	✅ Passed	All test names are stable and deterministic, using only static strings and hardcoded constants with no dynamic values incorporated.
Test Structure And Quality	✅ Passed	The modified file is a monitor test framework implementation, not a Ginkgo test file, so the Ginkgo test structure check is not applicable.
Microshift Test Compatibility	✅ Passed	This PR does not add any new Ginkgo e2e tests; it only modifies an existing monitoring infrastructure function to fix error string matching. The custom check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	PR modifies only an existing monitoring test's error string matching logic, does not add new Ginkgo e2e tests.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only test file to fix case-sensitive error string matching; no deployment manifests, operator code, controllers, or scheduling constraints affected.
Ote Binary Stdout Contract	✅ Passed	The PR modifies only error string matching logic within a test function without introducing any process-level stdout writes that would violate the OTE Binary Stdout Contract.
Title check	✅ Passed	The title accurately describes the main change: fixing case-sensitive error matching in a Whereabouts IP allocation test, which aligns with the modification of the error string comparison from capitalized to lowercase 'error'.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

openshift-merge-bot · 2026-04-15T09:56:53Z

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

tssurya

/lgtm

tssurya · 2026-04-15T11:31:30Z

 		if strings.Contains(event.Locator.Keys[monitorapi.LocatorPodKey], "whereabouts-pod") &&
 			strings.Contains(event.Message.HumanMessage, "error adding container to network") &&
-			strings.Contains(event.Message.HumanMessage, "Error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 ") {
+			strings.Contains(event.Message.HumanMessage, "error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 ") {


this error only surfaces when in CI the time taken for the delete of the pod takes more than 5seconds.
hence we weren't running into this issue, however really that test in whereabouts should fail.

tssurya · 2026-04-15T14:26:59Z

/approve

tssurya · 2026-04-15T14:27:36Z

@dgoodwin could you please approve this one?
it will help with some of the errors happening in https://redhat.atlassian.net/browse/OCPBUGS-83286

tssurya · 2026-04-15T14:35:31Z

retitle OCPBUGS-83286: Fix case-sensitive error matching in Whereabouts IP allocation test

tssurya · 2026-04-15T14:35:40Z

/retitle OCPBUGS-83286: Fix case-sensitive error matching in Whereabouts IP allocation test

openshift-ci-robot · 2026-04-15T14:35:57Z

@pperiyasamy: This pull request references Jira Issue OCPBUGS-83286, which is invalid:

expected the bug to target either version "5.0." or "openshift-5.0.", but it targets "4.22" instead

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:

Update the test to match the exact error string returned by the cmd add operation.

Reference:
https://github.com/openshift/whereabouts-cni/blob/release-4.22/cmd/whereabouts.go#L90

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network 
{  5 failures to create the sandbox
...
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-rn69f node/ci-op-s9md65n3-5bc1c-lsqlc-worker-eastus2-pdd8k pod/whereabouts-pod-cb6ld hmsg/32f45005d9 - race condition: sandbox failure at pod creation time (new pod created -34.35 seconds after deletion started) - firstTimestamp/2026-04-12T16:43:23Z interesting/true lastTimestamp/2026-04-12T16:43:23Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-cb6ld_e2e-test-whereabouts-e2e-rn69f_784dd26c-4e4d-4f92-90e9-ef57502c9845_0(1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99): error adding pod e2e-test-whereabouts-e2e-rn69f_whereabouts-pod-cb6ld to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99" Netns:"/var/run/netns/43532160-5396-417e-8cb3-221c162a04d8" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-rn69f;K8S_POD_NAME=whereabouts-pod-cb6ld;K8S_POD_INFRA_CONTAINER_ID=1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99;K8S_POD_UID=784dd26c-4e4d-4f92-90e9-ef57502c9845" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld] networking: [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld/784dd26c-4e4d-4f92-90e9-ef57502c9845:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-rn69f node/ci-op-s9md65n3-5bc1c-lsqlc-worker-eastus2-pdd8k pod/whereabouts-pod-cb6ld hmsg/f2578ad644 - race condition: sandbox failure at pod creation time (new pod created -30.35 seconds after deletion started) - firstTimestamp/2026-04-12T16:43:27Z interesting/true lastTimestamp/2026-04-12T16:43:27Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-cb6ld_e2e-test-whereabouts-e2e-rn69f_784dd26c-4e4d-4f92-90e9-ef57502c9845_0(920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae): error adding pod e2e-test-whereabouts-e2e-rn69f_whereabouts-pod-cb6ld to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae" Netns:"/var/run/netns/dd8abd81-1fbf-448e-97a8-2a580559ec28" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-rn69f;K8S_POD_NAME=whereabouts-pod-cb6ld;K8S_POD_INFRA_CONTAINER_ID=920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae;K8S_POD_UID=784dd26c-4e4d-4f92-90e9-ef57502c9845" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld] networking: [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld/784dd26c-4e4d-4f92-90e9-ef57502c9845:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]

'
'

Summary by CodeRabbit

Tests
Improved network testing to more reliably detect IP-range exhaustion errors during pod sandbox creation, enhancing test accuracy and reliability.

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.

tssurya · 2026-04-15T14:37:35Z

/jira refresh

openshift-ci-robot · 2026-04-15T14:37:44Z

@tssurya: This pull request references Jira Issue OCPBUGS-83286, 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 (5.0.0) matches configured target version for branch (5.0.0)
bug is in the state New, 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.

dgoodwin · 2026-04-15T14:55:51Z

/approve

openshift-ci · 2026-04-15T14:56:11Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, pperiyasamy, tssurya

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:

~~OWNERS~~ [dgoodwin]

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

pperiyasamy · 2026-04-15T15:12:35Z

/verified by ci

The job https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/31012/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044354401346260992 is not having whereabouts flake anymore.

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network expand_less
Run #0: Failed expand_less	0s
{  2 failures to create the sandbox

namespace/e2e-test-egress-router-cni-e2e-swlm8 node/ci-op-ih20hqn3-4537c-8rps2-worker-a-kgr4d pod/egress-router-cni-deployment-fdd9fb7c-sj5gc hmsg/b7ed77cb60 - race condition: sandbox failure at pod creation time (new pod created -70.40 seconds after deletion started) - firstTimestamp/2026-04-15T12:07:06Z interesting/true lastTimestamp/2026-04-15T12:07:06Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_egress-router-cni-deployment-fdd9fb7c-sj5gc_e2e-test-egress-router-cni-e2e-swlm8_6235092e-996c-4dc6-8928-179e582f6b6a_0(301ff302ffdd17620c24d40a3ff54bc7ac736d7c5439e02355eb2a8073ed453b): error adding pod e2e-test-egress-router-cni-e2e-swlm8_egress-router-cni-deployment-fdd9fb7c-sj5gc to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"301ff302ffdd17620c24d40a3ff54bc7ac736d7c5439e02355eb2a8073ed453b" Netns:"/var/run/netns/b3fd3fc3-0959-43b4-8a55-ccc9747296e3" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-egress-router-cni-e2e-swlm8;K8S_POD_NAME=egress-router-cni-deployment-fdd9fb7c-sj5gc;K8S_POD_INFRA_CONTAINER_ID=301ff302ffdd17620c24d40a3ff54bc7ac736d7c5439e02355eb2a8073ed453b;K8S_POD_UID=6235092e-996c-4dc6-8928-179e582f6b6a" Path:"" ERRORED: error configuring pod [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc] networking: [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc/6235092e-996c-4dc6-8928-179e582f6b6a:egress-router-cni-nad]: error adding container to network "egress-router-cni-nad": failed to unmarshal raw result: unexpected end of JSON input
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-egress-router-cni-e2e-swlm8 node/ci-op-ih20hqn3-4537c-8rps2-worker-a-kgr4d pod/egress-router-cni-deployment-fdd9fb7c-sj5gc hmsg/817d8f0ea7 - race condition: sandbox failure at pod creation time (new pod created -66.40 seconds after deletion started) - firstTimestamp/2026-04-15T12:07:10Z interesting/true lastTimestamp/2026-04-15T12:07:10Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_egress-router-cni-deployment-fdd9fb7c-sj5gc_e2e-test-egress-router-cni-e2e-swlm8_6235092e-996c-4dc6-8928-179e582f6b6a_0(1be47172bb6c6b3e5c9a1bfa2d9e7e53fe125e88f5ae4b7f87ad04b6318c3918): error adding pod e2e-test-egress-router-cni-e2e-swlm8_egress-router-cni-deployment-fdd9fb7c-sj5gc to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1be47172bb6c6b3e5c9a1bfa2d9e7e53fe125e88f5ae4b7f87ad04b6318c3918" Netns:"/var/run/netns/62b2e5c3-2322-40ac-aec8-cf7a21c874b5" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-egress-router-cni-e2e-swlm8;K8S_POD_NAME=egress-router-cni-deployment-fdd9fb7c-sj5gc;K8S_POD_INFRA_CONTAINER_ID=1be47172bb6c6b3e5c9a1bfa2d9e7e53fe125e88f5ae4b7f87ad04b6318c3918;K8S_POD_UID=6235092e-996c-4dc6-8928-179e582f6b6a" Path:"" ERRORED: error configuring pod [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc] networking: [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc/6235092e-996c-4dc6-8928-179e582f6b6a:egress-router-cni-nad]: error adding container to network "egress-router-cni-nad": failed to unmarshal raw result: unexpected end of JSON input
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}}
[open stdoutopen_in_new](https://prow.ci.openshift.org/spyglass/lens/junit/iframe?req=%7B%22artifacts%22%3A%5B%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_e2e_analysis__20260415-131154.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_symptoms.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-must-gather%2Fartifacts%2Fjunit_install.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fe2e-monitor-tests__20260415-111245.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fjunit_e2e__20260415-111245.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_node_ready.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_nodes.xml%22%2C%22artifacts%2Fjunit_operator.xml%22%2C%22prowjob_junit.xml%22%5D%2C%22index%22%3A2%2C%22src%22%3A%22gs%2Ftest-platform-results%2Fpr-logs%2Fpull%2F31012%2Fpull-ci-openshift-origin-main-e2e-gcp-ovn%2F2044354401346260992%22%7D&topURL=https%3A//prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/31012/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044354401346260992&lensIndex=2#)
Run #1: Passed expand_less	0s
<nil>

whereas it's seen with other jobs, for example https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30922/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044364306614587392:

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network expand_less
Run #0: Failed expand_less	0s
{  2 failures to create the sandbox

namespace/e2e-test-whereabouts-e2e-sxcg5 node/ci-op-5qb9txvh-4537c-wrbtl-worker-f-njns4 pod/whereabouts-pod-gj4t6 hmsg/204e81a236 - race condition: sandbox failure at pod creation time (new pod created -53.77 seconds after deletion started) - firstTimestamp/2026-04-15T12:58:36Z interesting/true lastTimestamp/2026-04-15T12:58:36Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-gj4t6_e2e-test-whereabouts-e2e-sxcg5_c0f49751-e203-42b3-8ab8-a3d278ff1cfb_0(3e3c9ad946ea147e840e79cb2ad23c41c039a4f046dfd7e4dc5102a55afe36a5): error adding pod e2e-test-whereabouts-e2e-sxcg5_whereabouts-pod-gj4t6 to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"3e3c9ad946ea147e840e79cb2ad23c41c039a4f046dfd7e4dc5102a55afe36a5" Netns:"/var/run/netns/9b709598-527b-4dad-9934-c19938ec528d" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-sxcg5;K8S_POD_NAME=whereabouts-pod-gj4t6;K8S_POD_INFRA_CONTAINER_ID=3e3c9ad946ea147e840e79cb2ad23c41c039a4f046dfd7e4dc5102a55afe36a5;K8S_POD_UID=c0f49751-e203-42b3-8ab8-a3d278ff1cfb" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6] networking: [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6/c0f49751-e203-42b3-8ab8-a3d278ff1cfb:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-sxcg5 node/ci-op-5qb9txvh-4537c-wrbtl-worker-f-njns4 pod/whereabouts-pod-gj4t6 hmsg/d0423029a6 - race condition: sandbox failure at pod creation time (new pod created -36.77 seconds after deletion started) - firstTimestamp/2026-04-15T12:58:53Z interesting/true lastTimestamp/2026-04-15T12:58:53Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-gj4t6_e2e-test-whereabouts-e2e-sxcg5_c0f49751-e203-42b3-8ab8-a3d278ff1cfb_0(1bacd2dedc1bc82b4a885c3093ab5fc0bf27897f44b899c2d3f8ff20e836dd56): error adding pod e2e-test-whereabouts-e2e-sxcg5_whereabouts-pod-gj4t6 to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1bacd2dedc1bc82b4a885c3093ab5fc0bf27897f44b899c2d3f8ff20e836dd56" Netns:"/var/run/netns/570b5c30-77a0-4e60-912b-da20720a6a18" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-sxcg5;K8S_POD_NAME=whereabouts-pod-gj4t6;K8S_POD_INFRA_CONTAINER_ID=1bacd2dedc1bc82b4a885c3093ab5fc0bf27897f44b899c2d3f8ff20e836dd56;K8S_POD_UID=c0f49751-e203-42b3-8ab8-a3d278ff1cfb" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6] networking: [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6/c0f49751-e203-42b3-8ab8-a3d278ff1cfb:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}}
[open stdoutopen_in_new](https://prow.ci.openshift.org/spyglass/lens/junit/iframe?req=%7B%22artifacts%22%3A%5B%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_e2e_analysis__20260415-140123.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_symptoms.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-must-gather%2Fartifacts%2Fjunit_install.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fe2e-monitor-tests__20260415-115903.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fjunit_e2e__20260415-115903.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_node_ready.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_nodes.xml%22%2C%22artifacts%2Fjunit_operator.xml%22%2C%22prowjob_junit.xml%22%5D%2C%22index%22%3A2%2C%22src%22%3A%22gs%2Ftest-platform-results%2Fpr-logs%2Fpull%2F30922%2Fpull-ci-openshift-origin-main-e2e-gcp-ovn%2F2044364306614587392%22%7D&topURL=https%3A//prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30922/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044364306614587392&lensIndex=2#)
Run #1: Passed expand_less	0s
<nil>

openshift-ci-robot · 2026-04-15T15:12:48Z

@pperiyasamy: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

The job https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/31012/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044354401346260992 is not having whereabouts flake anymore.

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network expand_less
Run #0: Failed expand_less	0s
{  2 failures to create the sandbox

namespace/e2e-test-egress-router-cni-e2e-swlm8 node/ci-op-ih20hqn3-4537c-8rps2-worker-a-kgr4d pod/egress-router-cni-deployment-fdd9fb7c-sj5gc hmsg/b7ed77cb60 - race condition: sandbox failure at pod creation time (new pod created -70.40 seconds after deletion started) - firstTimestamp/2026-04-15T12:07:06Z interesting/true lastTimestamp/2026-04-15T12:07:06Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_egress-router-cni-deployment-fdd9fb7c-sj5gc_e2e-test-egress-router-cni-e2e-swlm8_6235092e-996c-4dc6-8928-179e582f6b6a_0(301ff302ffdd17620c24d40a3ff54bc7ac736d7c5439e02355eb2a8073ed453b): error adding pod e2e-test-egress-router-cni-e2e-swlm8_egress-router-cni-deployment-fdd9fb7c-sj5gc to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"301ff302ffdd17620c24d40a3ff54bc7ac736d7c5439e02355eb2a8073ed453b" Netns:"/var/run/netns/b3fd3fc3-0959-43b4-8a55-ccc9747296e3" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-egress-router-cni-e2e-swlm8;K8S_POD_NAME=egress-router-cni-deployment-fdd9fb7c-sj5gc;K8S_POD_INFRA_CONTAINER_ID=301ff302ffdd17620c24d40a3ff54bc7ac736d7c5439e02355eb2a8073ed453b;K8S_POD_UID=6235092e-996c-4dc6-8928-179e582f6b6a" Path:"" ERRORED: error configuring pod [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc] networking: [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc/6235092e-996c-4dc6-8928-179e582f6b6a:egress-router-cni-nad]: error adding container to network "egress-router-cni-nad": failed to unmarshal raw result: unexpected end of JSON input
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-egress-router-cni-e2e-swlm8 node/ci-op-ih20hqn3-4537c-8rps2-worker-a-kgr4d pod/egress-router-cni-deployment-fdd9fb7c-sj5gc hmsg/817d8f0ea7 - race condition: sandbox failure at pod creation time (new pod created -66.40 seconds after deletion started) - firstTimestamp/2026-04-15T12:07:10Z interesting/true lastTimestamp/2026-04-15T12:07:10Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_egress-router-cni-deployment-fdd9fb7c-sj5gc_e2e-test-egress-router-cni-e2e-swlm8_6235092e-996c-4dc6-8928-179e582f6b6a_0(1be47172bb6c6b3e5c9a1bfa2d9e7e53fe125e88f5ae4b7f87ad04b6318c3918): error adding pod e2e-test-egress-router-cni-e2e-swlm8_egress-router-cni-deployment-fdd9fb7c-sj5gc to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1be47172bb6c6b3e5c9a1bfa2d9e7e53fe125e88f5ae4b7f87ad04b6318c3918" Netns:"/var/run/netns/62b2e5c3-2322-40ac-aec8-cf7a21c874b5" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-egress-router-cni-e2e-swlm8;K8S_POD_NAME=egress-router-cni-deployment-fdd9fb7c-sj5gc;K8S_POD_INFRA_CONTAINER_ID=1be47172bb6c6b3e5c9a1bfa2d9e7e53fe125e88f5ae4b7f87ad04b6318c3918;K8S_POD_UID=6235092e-996c-4dc6-8928-179e582f6b6a" Path:"" ERRORED: error configuring pod [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc] networking: [e2e-test-egress-router-cni-e2e-swlm8/egress-router-cni-deployment-fdd9fb7c-sj5gc/6235092e-996c-4dc6-8928-179e582f6b6a:egress-router-cni-nad]: error adding container to network "egress-router-cni-nad": failed to unmarshal raw result: unexpected end of JSON input
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}}
[open stdoutopen_in_new](https://prow.ci.openshift.org/spyglass/lens/junit/iframe?req=%7B%22artifacts%22%3A%5B%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_e2e_analysis__20260415-131154.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_symptoms.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-must-gather%2Fartifacts%2Fjunit_install.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fe2e-monitor-tests__20260415-111245.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fjunit_e2e__20260415-111245.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_node_ready.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_nodes.xml%22%2C%22artifacts%2Fjunit_operator.xml%22%2C%22prowjob_junit.xml%22%5D%2C%22index%22%3A2%2C%22src%22%3A%22gs%2Ftest-platform-results%2Fpr-logs%2Fpull%2F31012%2Fpull-ci-openshift-origin-main-e2e-gcp-ovn%2F2044354401346260992%22%7D&topURL=https%3A//prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/31012/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044354401346260992&lensIndex=2#)
Run #1: Passed expand_less	0s
<nil>

whereas it's seen with other jobs, for example https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30922/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044364306614587392:

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network expand_less
Run #0: Failed expand_less	0s
{  2 failures to create the sandbox

namespace/e2e-test-whereabouts-e2e-sxcg5 node/ci-op-5qb9txvh-4537c-wrbtl-worker-f-njns4 pod/whereabouts-pod-gj4t6 hmsg/204e81a236 - race condition: sandbox failure at pod creation time (new pod created -53.77 seconds after deletion started) - firstTimestamp/2026-04-15T12:58:36Z interesting/true lastTimestamp/2026-04-15T12:58:36Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-gj4t6_e2e-test-whereabouts-e2e-sxcg5_c0f49751-e203-42b3-8ab8-a3d278ff1cfb_0(3e3c9ad946ea147e840e79cb2ad23c41c039a4f046dfd7e4dc5102a55afe36a5): error adding pod e2e-test-whereabouts-e2e-sxcg5_whereabouts-pod-gj4t6 to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"3e3c9ad946ea147e840e79cb2ad23c41c039a4f046dfd7e4dc5102a55afe36a5" Netns:"/var/run/netns/9b709598-527b-4dad-9934-c19938ec528d" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-sxcg5;K8S_POD_NAME=whereabouts-pod-gj4t6;K8S_POD_INFRA_CONTAINER_ID=3e3c9ad946ea147e840e79cb2ad23c41c039a4f046dfd7e4dc5102a55afe36a5;K8S_POD_UID=c0f49751-e203-42b3-8ab8-a3d278ff1cfb" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6] networking: [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6/c0f49751-e203-42b3-8ab8-a3d278ff1cfb:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-sxcg5 node/ci-op-5qb9txvh-4537c-wrbtl-worker-f-njns4 pod/whereabouts-pod-gj4t6 hmsg/d0423029a6 - race condition: sandbox failure at pod creation time (new pod created -36.77 seconds after deletion started) - firstTimestamp/2026-04-15T12:58:53Z interesting/true lastTimestamp/2026-04-15T12:58:53Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-gj4t6_e2e-test-whereabouts-e2e-sxcg5_c0f49751-e203-42b3-8ab8-a3d278ff1cfb_0(1bacd2dedc1bc82b4a885c3093ab5fc0bf27897f44b899c2d3f8ff20e836dd56): error adding pod e2e-test-whereabouts-e2e-sxcg5_whereabouts-pod-gj4t6 to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1bacd2dedc1bc82b4a885c3093ab5fc0bf27897f44b899c2d3f8ff20e836dd56" Netns:"/var/run/netns/570b5c30-77a0-4e60-912b-da20720a6a18" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-sxcg5;K8S_POD_NAME=whereabouts-pod-gj4t6;K8S_POD_INFRA_CONTAINER_ID=1bacd2dedc1bc82b4a885c3093ab5fc0bf27897f44b899c2d3f8ff20e836dd56;K8S_POD_UID=c0f49751-e203-42b3-8ab8-a3d278ff1cfb" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6] networking: [e2e-test-whereabouts-e2e-sxcg5/whereabouts-pod-gj4t6/c0f49751-e203-42b3-8ab8-a3d278ff1cfb:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}}
[open stdoutopen_in_new](https://prow.ci.openshift.org/spyglass/lens/junit/iframe?req=%7B%22artifacts%22%3A%5B%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_e2e_analysis__20260415-140123.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-extra%2Fartifacts%2Fjunit%2Fjunit_symptoms.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fgather-must-gather%2Fartifacts%2Fjunit_install.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fe2e-monitor-tests__20260415-115903.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit%2Fjunit_e2e__20260415-115903.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_node_ready.xml%22%2C%22artifacts%2Fe2e-gcp-ovn%2Fopenshift-e2e-test%2Fartifacts%2Fjunit_nodes.xml%22%2C%22artifacts%2Fjunit_operator.xml%22%2C%22prowjob_junit.xml%22%5D%2C%22index%22%3A2%2C%22src%22%3A%22gs%2Ftest-platform-results%2Fpr-logs%2Fpull%2F30922%2Fpull-ci-openshift-origin-main-e2e-gcp-ovn%2F2044364306614587392%22%7D&topURL=https%3A//prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/30922/pull-ci-openshift-origin-main-e2e-gcp-ovn/2044364306614587392&lensIndex=2#)
Run #1: Passed expand_less	0s
<nil>

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-bot · 2026-04-15T15:34:19Z

/retest-required

Remaining retests: 0 against base HEAD 9df27cd and 2 for PR HEAD 5657022 in total

tssurya · 2026-04-15T16:19:53Z

/cherry-pick release-4.22

openshift-cherrypick-robot · 2026-04-15T16:19:57Z

@tssurya: once the present PR merges, I will cherry-pick it on top of release-4.22 in a new PR and assign it to you.

Details

In response to this:

/cherry-pick release-4.22

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.

openshift-merge-bot · 2026-04-15T23:34:02Z

/retest-required

Remaining retests: 0 against base HEAD 53cc9e6 and 1 for PR HEAD 5657022 in total

pperiyasamy · 2026-04-16T07:20:57Z

/test e2e-vsphere-ovn-upi

tssurya · 2026-04-16T10:59:24Z

/test e2e-vsphere-ovn-upi

pperiyasamy · 2026-04-16T14:52:43Z

/test e2e-vsphere-ovn-upi

openshift-merge-bot · 2026-04-16T18:54:08Z

/retest-required

Remaining retests: 0 against base HEAD d7ad0db and 0 for PR HEAD 5657022 in total

openshift-trt · 2026-04-16T22:13:28Z

Job Failure Risk Analysis for sha: 5657022

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi	Low [sig-instrumentation] Prometheus [apigroup:image.openshift.io] when installed on the cluster shouldn't report any alerts in firing state apart from Watchdog and AlertmanagerReceiversNotConfigured [Early][apigroup:config.openshift.io] [Suite:openshift/conformance/parallel] This test has passed 0.00% of 14 runs on release 5.0 [Architecture:amd64 FeatureSet:default Installer:upi JobTier:standard Network:ovn NetworkStack:ipv4 OS:rhcos9 Owner:eng Platform:vsphere Procedure:none SecurityMode:default Topology:ha Upgrade:none] in the last week.

openshift-merge-bot · 2026-04-16T22:51:48Z

/hold

Revision 5657022 was retested 3 times: holding

pperiyasamy · 2026-04-17T08:23:23Z

/hold cancel

pperiyasamy · 2026-04-17T08:23:35Z

/test e2e-vsphere-ovn-upi

openshift-merge-bot · 2026-04-17T12:03:19Z

/retest-required

Remaining retests: 0 against base HEAD d7ad0db and 2 for PR HEAD 5657022 in total

neisw · 2026-04-17T12:11:36Z

/override ci/prow/e2e-vsphere-ovn-upi

openshift-ci · 2026-04-17T12:11:53Z

@neisw: Overrode contexts on behalf of neisw: ci/prow/e2e-vsphere-ovn-upi

Details

In response to this:

/override ci/prow/e2e-vsphere-ovn-upi

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.

openshift-ci-robot · 2026-04-17T12:49:59Z

@pperiyasamy: Jira Issue Verification Checks: Jira Issue OCPBUGS-83286
✔️ 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-83286 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:

Update the test to match the exact error string returned by the cmd add operation.

Reference:
https://github.com/openshift/whereabouts-cni/blob/release-4.22/cmd/whereabouts.go#L90

: [Monitor:legacy-networking-invariants][sig-network] pods should successfully create sandboxes by adding pod to network 
{  5 failures to create the sandbox
...
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-rn69f node/ci-op-s9md65n3-5bc1c-lsqlc-worker-eastus2-pdd8k pod/whereabouts-pod-cb6ld hmsg/32f45005d9 - race condition: sandbox failure at pod creation time (new pod created -34.35 seconds after deletion started) - firstTimestamp/2026-04-12T16:43:23Z interesting/true lastTimestamp/2026-04-12T16:43:23Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-cb6ld_e2e-test-whereabouts-e2e-rn69f_784dd26c-4e4d-4f92-90e9-ef57502c9845_0(1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99): error adding pod e2e-test-whereabouts-e2e-rn69f_whereabouts-pod-cb6ld to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99" Netns:"/var/run/netns/43532160-5396-417e-8cb3-221c162a04d8" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-rn69f;K8S_POD_NAME=whereabouts-pod-cb6ld;K8S_POD_INFRA_CONTAINER_ID=1f8d5feb513d355dedff9d5ec4a076407c50ead09de650df44a5f4214764df99;K8S_POD_UID=784dd26c-4e4d-4f92-90e9-ef57502c9845" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld] networking: [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld/784dd26c-4e4d-4f92-90e9-ef57502c9845:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]
': StdinData: {"auxiliaryCNIChainName":"vendor-cni-chain","binDir":"/var/lib/cni/bin","clusterNetwork":"/host/run/multus/cni/net.d/10-ovn-kubernetes.conf","cniVersion":"0.3.1","daemonSocketDir":"/run/multus/socket","globalNamespaces":"default,openshift-multus,openshift-sriov-network-operator,openshift-cnv","logLevel":"verbose","logToStderr":true,"name":"multus-cni-network","namespaceIsolation":true,"type":"multus-shim"}
namespace/e2e-test-whereabouts-e2e-rn69f node/ci-op-s9md65n3-5bc1c-lsqlc-worker-eastus2-pdd8k pod/whereabouts-pod-cb6ld hmsg/f2578ad644 - race condition: sandbox failure at pod creation time (new pod created -30.35 seconds after deletion started) - firstTimestamp/2026-04-12T16:43:27Z interesting/true lastTimestamp/2026-04-12T16:43:27Z reason/FailedCreatePodSandBox Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_whereabouts-pod-cb6ld_e2e-test-whereabouts-e2e-rn69f_784dd26c-4e4d-4f92-90e9-ef57502c9845_0(920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae): error adding pod e2e-test-whereabouts-e2e-rn69f_whereabouts-pod-cb6ld to CNI network "multus-cni-network": plugin type="multus-shim" name="multus-cni-network" failed (add): CmdAdd (shim): CNI request failed with status 400: 'ContainerID:"920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae" Netns:"/var/run/netns/dd8abd81-1fbf-448e-97a8-2a580559ec28" IfName:"eth0" Args:"IgnoreUnknown=1;K8S_POD_NAMESPACE=e2e-test-whereabouts-e2e-rn69f;K8S_POD_NAME=whereabouts-pod-cb6ld;K8S_POD_INFRA_CONTAINER_ID=920cde6f35a6a0c1f4c68a61bf0f2317fff087cfd9db6c817a8fb06401f71fae;K8S_POD_UID=784dd26c-4e4d-4f92-90e9-ef57502c9845" Path:"" ERRORED: error configuring pod [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld] networking: [e2e-test-whereabouts-e2e-rn69f/whereabouts-pod-cb6ld/784dd26c-4e4d-4f92-90e9-ef57502c9845:whereaboutstestbridge]: error adding container to network "whereaboutstestbridge": error at storage engine: Could not allocate IP in range: ip: 192.168.2.225 / - 192.168.2.230 / range: 192.168.2.224/29 / excludeRanges: [192.168.2.225/30]

'
'

Summary by CodeRabbit

Tests
Improved network testing to more reliably detect IP-range exhaustion errors during pod sandbox creation, enhancing test accuracy and reliability.

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 · 2026-04-17T12:50:13Z

@pperiyasamy: all tests passed!

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-cherrypick-robot · 2026-04-17T12:53:07Z

@tssurya: new pull request created: #31029

Details

In response to this:

/cherry-pick release-4.22

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.

openshift-ci bot requested review from deads2k and sjenning April 15, 2026 09:31

tssurya approved these changes Apr 15, 2026

View reviewed changes

openshift-ci bot assigned tssurya Apr 15, 2026

openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2026

openshift-ci bot changed the title ~~Fix case-sensitive error matching in Whereabouts IP allocation test~~ OCPBUGS-83286: Fix case-sensitive error matching in Whereabouts IP allocation test Apr 15, 2026

openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 15, 2026

openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Apr 15, 2026

openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 15, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 15, 2026

openshift-ci-robot mentioned this pull request Apr 16, 2026

OCPBUGS-83286: Fix swallowed errors in cmdAdd/cmdDel causing empty CNI result openshift/egress-router-cni#95

Merged

openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 16, 2026

openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 17, 2026

openshift-merge-bot bot merged commit 52460f7 into openshift:main Apr 17, 2026
21 checks passed

openshift-cherrypick-robot mentioned this pull request Apr 17, 2026

[release-4.22] OCPBUGS-83586: Fix case-sensitive error matching in Whereabouts IP allocation test #31029

Open

Conversation

pperiyasamy commented Apr 15, 2026 • edited by coderabbitai bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Uh oh!

openshift-merge-bot bot commented Apr 15, 2026

Uh oh!

coderabbitai bot commented Apr 15, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

❌ Failed checks (1 warning, 1 inconclusive)

Uh oh!

openshift-merge-bot bot commented Apr 15, 2026

Uh oh!

tssurya left a comment

Choose a reason for hiding this comment

Uh oh!

tssurya Apr 15, 2026

Choose a reason for hiding this comment

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Summary by CodeRabbit

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

dgoodwin commented Apr 15, 2026

Uh oh!

openshift-ci bot commented Apr 15, 2026

Uh oh!

pperiyasamy commented Apr 15, 2026

Uh oh!

openshift-ci-robot commented Apr 15, 2026

Uh oh!

openshift-merge-bot bot commented Apr 15, 2026

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

openshift-cherrypick-robot commented Apr 15, 2026

Uh oh!

openshift-merge-bot bot commented Apr 15, 2026

Uh oh!

pperiyasamy commented Apr 16, 2026

Uh oh!

tssurya commented Apr 16, 2026

Uh oh!

pperiyasamy commented Apr 16, 2026

Uh oh!

openshift-merge-bot bot commented Apr 16, 2026

Uh oh!

openshift-trt bot commented Apr 16, 2026

Uh oh!

openshift-merge-bot bot commented Apr 16, 2026

Uh oh!

pperiyasamy commented Apr 17, 2026

Uh oh!

pperiyasamy commented Apr 17, 2026

Uh oh!

openshift-merge-bot bot commented Apr 17, 2026

Uh oh!

neisw commented Apr 17, 2026

Uh oh!

openshift-ci bot commented Apr 17, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 17, 2026

Summary by CodeRabbit

Uh oh!

openshift-ci bot commented Apr 17, 2026

pperiyasamy commented Apr 15, 2026 •

edited by coderabbitai bot

Loading

coderabbitai bot commented Apr 15, 2026 •

edited

Loading