[release-0.95] Pin OVN-K to openshift release-4.17 for ipam e2e tests#2843
[release-0.95] Pin OVN-K to openshift release-4.17 for ipam e2e tests#2843RamLavi wants to merge 2 commits into
Conversation
kubevirt-prow
Bot
added
dco-signoff: yes
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the end-to-end functional tests script for the kubevirt-ipam-controller by removing the -ic flag from the KIND_ARGS environment variable. I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
kubevirt-prow
Bot
added
release-note-none
RamLavi
changed the title
|
/approve |
kubevirt-prow
Bot
added
the
approved
|
you sure it aint required on this old branch ? |
The ipam-controller e2e tests clone OVN-Kubernetes from master to set up the kind cluster. OVN-K master has evolved significantly since Nov 2025 (including a Helm migration in Apr 2026), making it incompatible with the older ipam-extensions commit and KubeVirt v1.3.x pinned on this branch. Pin to openshift/ovn-kubernetes release-4.17, which matches the CNV 4.17 stack this stable branch targets. Assisted-by: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Ram Lavi <ralavi@redhat.com>
RamLavi
force-pushed
the
fix-ipam-e2e-remove-ic-flag
branch
from
d21892f to
067c434
Compare
RamLavi
changed the title
|
/approve cancel I need to discuss this approach with other maintainers |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
kubevirt-prow
Bot
removed
the
approved
The -ic (interconnect) flag enables OVN interconnect mode which causes CoreDNS and other pods to get stuck in ContainerCreating on the release-4.17 OVN-K branch, preventing cluster-up from completing. Assisted-by: Claude Opus 4.6 <noreply@anthropic.com> Signed-off-by: Ram Lavi <ralavi@redhat.com>
|
|
@RamLavi: The following test failed, say
DetailsInstructions 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. |
2 participants
What this PR does / why we need it:
The ipam-controller e2e tests clone OVN-Kubernetes from upstream master to set up the kind cluster. OVN-K master has evolved significantly since Nov 2025 (including a Helm migration in Apr 2026), making it incompatible with the older ipam-extensions commit and KubeVirt v1.3.x pinned on this stable branch.
This PR pins OVN-K to
openshift/ovn-kubernetesrelease-4.17, which matches the CNV 4.17 stack this stable branch targets.Special notes for your reviewer:
The
-ic(interconnect) flag is kept — it's valid on therelease-4.17branch. It was only removed on upstream master.Release note: