OCPBUGS-83598: ovn-kubernetes: use OCP-matching CNV version for BGP virt 4.22 jobs by mkowalski · Pull Request #77970 · openshift/release

mkowalski · 2026-04-17T13:29:20Z

Summary

Bug: https://issues.redhat.com/browse/OCPBUGS-83598

Change CNV_PRERELEASE_LATEST_CHANNEL from "true" to "false" for the 4 BGP virt periodic jobs on release-4.22
When set to "true", the kubevirt-install step hardcodes cnv_version=4.99, installing a non-existent CNV version
Setting to "false" makes the step derive the version dynamically via ocp_version(), correctly resolving to 4.22

Affected jobs:

e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview
e2e-metal-ipi-ovn-bgp-virt-ipv4
e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview
e2e-metal-ipi-ovn-bgp-virt-dualstack

Test plan

Verify the affected periodic jobs install CNV 4.22 (nightly-4.22 channel, nightly-catalog:4.22 image)
Confirm CNV operator reaches Succeeded phase during job execution

🤖 Generated with Claude Code

The BGP virt periodic jobs were setting CNV_PRERELEASE_LATEST_CHANNEL to "true", which hardcodes cnv_version=4.99 in the kubevirt-install step. This installs a non-existent CNV version instead of the one matching the OCP cluster. Setting to "false" makes the install script derive the version dynamically from the cluster (4.22). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

coderabbitai · 2026-04-17T13:29:58Z

Walkthrough

Updated the test execution environment for four OVN-Kubernetes metal IPI "virt" e2e workflows by changing the CNV_PRERELEASE_LATEST_CHANNEL configuration value from "true" to "false" across all affected test steps.

Changes

Cohort / File(s)	Summary
CI Configuration Update `ci-operator/config/openshift/ovn-kubernetes/openshift-ovn-kubernetes-release-4.22__periodics.yaml`	Changed `CNV_PRERELEASE_LATEST_CHANNEL` from `"true"` to `"false"` in four metal IPI "virt" e2e test workflows.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

🚥 Pre-merge checks | ✅ 10

✅ Passed checks (10 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Stable And Deterministic Test Names	✅ Passed	PR modifies CI/CD configuration files (YAML), not Ginkgo test code. The custom check for stable and deterministic Ginkgo test names is not applicable to configuration files.
Test Structure And Quality	✅ Passed	This PR modifies only a YAML CI/CD configuration file with no Ginkgo test code present, making the custom check not applicable.
Microshift Test Compatibility	✅ Passed	PR only modifies CI configuration values in YAML file without adding or changing any Ginkgo test code.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	This pull request only modifies a YAML CI configuration file for the ovn-kubernetes project. The changes update the CNV_PRERELEASE_LATEST_CHANNEL environment variable for four periodic jobs to ensure they use CNV version 4.22 instead of a non-existent pre-release version. There are no new Ginkgo e2e tests added.
Topology-Aware Scheduling Compatibility	✅ Passed	PR modifies only CI/CD job configuration, not deployment manifests, operator code, or controllers, so scheduling constraint check is not applicable.
Ote Binary Stdout Contract	✅ Passed	This check is not applicable to the PR. The PR modifies only a YAML configuration file updating environment variable values; the OTE Binary Stdout Contract check targets executable test binary code violations.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	This PR does not add any new Ginkgo e2e tests. The changes are exclusively to CI configuration in a YAML file, modifying environment variables that affect how existing test workflows execute. Since the custom check applies only when new Ginkgo e2e tests are added and no new test code is present, the check is not applicable.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly relates to the main change: updating CNV version configuration for OVN-Kubernetes BGP virt jobs on release-4.22 by modifying the CNV_PRERELEASE_LATEST_CHANNEL setting.

_{✏️ 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-ci-robot · 2026-04-17T13:30:49Z

@mkowalski: This pull request references Jira Issue OCPBUGS-83598, which is invalid:

expected the bug to target the "5.0.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:

Summary

Bug: https://issues.redhat.com/browse/OCPBUGS-83598

Change CNV_PRERELEASE_LATEST_CHANNEL from "true" to "false" for the 4 BGP virt periodic jobs on release-4.22

When set to "true", the kubevirt-install step hardcodes cnv_version=4.99, installing a non-existent CNV version

Setting to "false" makes the step derive the version dynamically via ocp_version(), correctly resolving to 4.22

Affected jobs:

e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

e2e-metal-ipi-ovn-bgp-virt-ipv4

e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview

e2e-metal-ipi-ovn-bgp-virt-dualstack

Test plan

Verify the affected periodic jobs install CNV 4.22 (nightly-4.22 channel, nightly-catalog:4.22 image)

Confirm CNV operator reaches Succeeded phase during job execution

🤖 Generated with Claude Code

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-17T13:32:17Z

[REHEARSALNOTIFIER]
@mkowalski: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4	N/A	periodic	Ci-operator config changed
periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview	N/A	periodic	Ci-operator config changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

mkowalski · 2026-04-17T13:38:49Z

/jira refresh
/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4 periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack

openshift-merge-bot · 2026-04-17T13:38:53Z

@mkowalski: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

openshift-ci-robot · 2026-04-17T13:38:57Z

@mkowalski: This pull request references Jira Issue OCPBUGS-83598, 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
/pj-rehearse periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-ipv4 periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview periodic-ci-openshift-ovn-kubernetes-release-4.22-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack

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-21T11:01:26Z

/approve

We really should get CNV to lgtm though, I'll see who I can find.

mkowalski · 2026-04-21T12:47:26Z

/approve

We really should get CNV to lgtm though, I'll see who I can find.

Just pinged OVN-K for that. It's one of those spaghetti tests I told you about where we have core&blocking test depending on "optional" product...

maiqueb

tks. This makes sense since 4.99 now applies to openshift 4.23 (i.e. after branch is cut from main).

mkowalski · 2026-04-21T12:53:16Z

/pj-rehearse ack

openshift-merge-bot · 2026-04-21T12:53:19Z

@mkowalski: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

jcaamano · 2026-04-21T13:02:14Z

/approve

maiqueb · 2026-04-21T13:50:55Z

/lgtm

openshift-ci · 2026-04-21T13:52:54Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, jcaamano, maiqueb, mkowalski

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:

~~ci-operator/config/openshift/ovn-kubernetes/OWNERS~~ [jcaamano]

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

mkowalski · 2026-04-21T15:11:03Z

/retest-required

openshift-ci-robot · 2026-04-21T16:12:23Z

@mkowalski: Jira Issue OCPBUGS-83598: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

openshift/origin#31018 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-83598 has not been moved to the MODIFIED state.

Details

In response to this:

Summary

Bug: https://issues.redhat.com/browse/OCPBUGS-83598

Change CNV_PRERELEASE_LATEST_CHANNEL from "true" to "false" for the 4 BGP virt periodic jobs on release-4.22

When set to "true", the kubevirt-install step hardcodes cnv_version=4.99, installing a non-existent CNV version

Setting to "false" makes the step derive the version dynamically via ocp_version(), correctly resolving to 4.22

Affected jobs:

e2e-metal-ipi-ovn-bgp-virt-ipv4-techpreview

e2e-metal-ipi-ovn-bgp-virt-ipv4

e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview

e2e-metal-ipi-ovn-bgp-virt-dualstack

Test plan

Verify the affected periodic jobs install CNV 4.22 (nightly-4.22 channel, nightly-catalog:4.22 image)

Confirm CNV operator reaches Succeeded phase during job execution

🤖 Generated with Claude Code

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 Bot requested review from kyrtapz and tssurya April 17, 2026 13:30

mkowalski changed the title ~~ovn-kubernetes: use OCP-matching CNV version for BGP virt 4.22 jobs~~ OCPBUGS-83598: ovn-kubernetes: use OCP-matching CNV version for BGP virt 4.22 jobs Apr 17, 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 17, 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 17, 2026

maiqueb approved these changes Apr 21, 2026

View reviewed changes

openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label Apr 21, 2026

openshift-ci Bot assigned maiqueb Apr 21, 2026

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

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

openshift-merge-bot Bot merged commit 24cd161 into openshift:main Apr 21, 2026
11 of 18 checks passed

mkowalski deleted the fix-cnv-version-ovn-bgp-4.22 branch April 22, 2026 12:55

Conversation

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

Uh oh!

Summary

Test plan

Uh oh!

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

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

openshift-ci-robot commented Apr 17, 2026

Summary

Test plan

Uh oh!

openshift-merge-bot Bot commented Apr 17, 2026

Uh oh!

mkowalski commented Apr 17, 2026

Uh oh!

openshift-merge-bot Bot commented Apr 17, 2026

Uh oh!

openshift-ci-robot commented Apr 17, 2026

Uh oh!

dgoodwin commented Apr 21, 2026

Uh oh!

mkowalski commented Apr 21, 2026

Uh oh!

maiqueb left a comment

Choose a reason for hiding this comment

Uh oh!

mkowalski commented Apr 21, 2026

Uh oh!

openshift-merge-bot Bot commented Apr 21, 2026

Uh oh!

jcaamano commented Apr 21, 2026

Uh oh!

maiqueb commented Apr 21, 2026

Uh oh!

openshift-ci Bot commented Apr 21, 2026

Uh oh!

mkowalski commented Apr 21, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 21, 2026

Summary

Test plan

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

5 participants

mkowalski commented Apr 17, 2026 •

edited

Loading

coderabbitai Bot commented Apr 17, 2026 •

edited

Loading