OCPBUGS-84636, CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP by igsilya · Pull Request #3075 · openshift/ovn-kubernetes

igsilya · 2026-03-20T11:44:55Z

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

Note however, that this PR doesn't really change anything right now, as 23.06.4-26.el8fdp is the latest available version.

Manual cherry pick of the change from 4.13: #3074

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months. Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP. Signed-off-by: Ilya Maximets <i.maximets@ovn.org>

openshift-ci-robot · 2026-03-20T11:45:00Z

@igsilya: This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.12.z" version, but no target version was set.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will bring updated OVN builds and will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

Manual cherry pick of the change from 4.13: #3074

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.

coderabbitai · 2026-03-20T11:45:13Z

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: d88838c8-5993-487f-8353-19146787356c

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

📝 Coding Plan

Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

igsilya · 2026-03-23T20:40:48Z

/retest-required

igsilya · 2026-04-08T12:21:56Z

/test e2e-gcp-ovn
Some storage issues in this one.

openshift-ci-robot · 2026-04-08T15:13:45Z

@igsilya: This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.12.z" version, but no target version was set.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

Note however, that this PR doesn't really change anything right now, as 23.06.4-26.el8fdp is the latest available version.

Manual cherry pick of the change from 4.13: #3074

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.

igsilya · 2026-04-08T15:15:56Z

This PR doesn't change anything, since 23.06.4-26.el8fdp is the latest available version anyway. The tests are just flaky (was able to make them pass in #3122).

/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade
/test e2e-gcp-ovn

igsilya · 2026-04-08T18:52:40Z

/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade
/test e2e-gcp-ovn

tssurya

/lgtm
/label backport-risk-assessed

there is always risk with consuming unpinned versions - but the team has done everything possible for pre-merge testing signal setup

PS: wow yum install!!

tssurya · 2026-04-13T12:12:02Z

/approve

openshift-ci · 2026-04-13T12:12:24Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: igsilya, 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~~ [tssurya]

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

igsilya · 2026-04-14T14:31:16Z

/retest-required

jluhrsen · 2026-04-14T20:21:34Z

@tssurya , here is the bug we can use to override the unit/gofmt/lint jobs

tssurya · 2026-04-15T11:04:37Z

/retest-required

igsilya · 2026-04-28T16:00:42Z

/jira cherry-pick OCPBUGS-84635

openshift-ci-robot · 2026-04-28T16:01:53Z

@igsilya: Jira Issue OCPBUGS-84635 has been cloned as Jira Issue OCPBUGS-84636. Will retitle bug to link to clone.
/retitle OCPBUGS-84636: CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP

Details

In response to this:

/jira cherry-pick OCPBUGS-84635

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 · 2026-04-28T16:02:09Z

@igsilya: This pull request references Jira Issue OCPBUGS-84636, which is invalid:

expected dependent Jira Issue OCPBUGS-84635 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

Note however, that this PR doesn't really change anything right now, as 23.06.4-26.el8fdp is the latest available version.

Manual cherry pick of the change from 4.13: #3074

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 · 2026-04-28T16:04:27Z

@igsilya: This pull request references Jira Issue OCPBUGS-84636, which is invalid:

expected dependent Jira Issue OCPBUGS-84635 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED 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.

This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.12.z" version, but no target version was set.

Details

In response to this:

OVN-Kubernetes is always lagging behind on the version of OVN it pins. This is causing a lot of trouble with keeping up with bug fixes and especially CVE fixes on older branches, resulting in scanners flagging this image with poor security grades and much longer time for bug fixes to be delivered to customers as the PR backporting process can take weeks or even months.

Removing the pin, so every time the new build is released in FDP, it automatically gets into versions of OpneShift that use it. There is a pre-release testing process in place between FDP and OCP QE that ensures the required test coverage before the new build is released through FDP.

This PR will allow picking up newer ones automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

Note however, that this PR doesn't really change anything right now, as 23.06.4-26.el8fdp is the latest available version.

Manual cherry pick of the change from 4.13: #3074

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.

igsilya · 2026-04-28T16:06:35Z

The only verification required here is that the images are still building, since all the RPM versions stay the same, and CI verified that.
/verified by CI

The fmt/lint/unit tests are borked, but just in case
/retest-required

openshift-ci-robot · 2026-04-28T16:06:48Z

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

Details

In response to this:

The only verification required here is that the images are still building, since all the RPM versions stay the same, and CI verified that.
/verified by CI

The fmt/lint/unit tests are borked, but just in case
/retest-required

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.

igsilya · 2026-04-30T10:23:10Z

/jira refresh

openshift-ci-robot · 2026-04-30T10:23:17Z

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

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.12.z) matches configured target version for branch (4.12.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-84635 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
dependent Jira Issue OCPBUGS-84635 targets the "4.13.z" version, which is one of the valid target versions: 4.13.0, 4.13.z
bug has dependents

This pull request references CORENET-6055 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.12.z" version, but no target version was set.

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-merge-bot · 2026-04-30T11:28:02Z

/retest-required

Remaining retests: 0 against base HEAD cced5e1 and 2 for PR HEAD ad77729 in total

openshift-ci · 2026-04-30T11:32:45Z

@igsilya: 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/security	`ad77729`	link	false	`/test security`
ci/prow/unit	`ad77729`	link	true	`/test unit`
ci/prow/gofmt	`ad77729`	link	true	`/test gofmt`
ci/prow/lint	`ad77729`	link	true	`/test lint`

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 added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 20, 2026

openshift-ci Bot requested review from abhat and tssurya March 20, 2026 11:46

tssurya reviewed Apr 13, 2026

View reviewed changes

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 13, 2026

openshift-ci Bot assigned anuragthehatter, asood-rh, barbora137, jechen0648, mffiedler and rbbratta Apr 13, 2026

openshift-ci Bot assigned weliang1 and tssurya Apr 13, 2026

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

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

igsilya mentioned this pull request Apr 16, 2026

[openshift-4.12] CORENET-6055: ovn-kubernetes: Remove exemptions for now unpinned OVN rpms. openshift-eng/ocp-build-data#10062

Open

openshift-ci Bot changed the title ~~CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP~~ OCPBUGS-84636: CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP Apr 28, 2026

openshift-ci-robot added the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Apr 28, 2026

igsilya changed the title ~~OCPBUGS-84636: CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP~~ OCPBUGS-84636, CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP Apr 28, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Apr 28, 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 30, 2026

Conversation

igsilya commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 20, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

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

Uh oh!

Review skipped

Uh oh!

igsilya commented Mar 23, 2026

Uh oh!

igsilya commented Apr 8, 2026

Uh oh!

openshift-ci-robot commented Apr 8, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

igsilya commented Apr 8, 2026

Uh oh!

igsilya commented Apr 8, 2026

Uh oh!

tssurya left a comment

Choose a reason for hiding this comment

Uh oh!

tssurya commented Apr 13, 2026

Uh oh!

openshift-ci Bot commented Apr 13, 2026

Uh oh!

igsilya commented Apr 14, 2026

Uh oh!

jluhrsen commented Apr 14, 2026

Uh oh!

tssurya commented Apr 15, 2026

Uh oh!

igsilya commented Apr 28, 2026

Uh oh!

openshift-ci-robot commented Apr 28, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 28, 2026

Uh oh!

openshift-ci-robot commented Apr 28, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

igsilya commented Apr 28, 2026

Uh oh!

openshift-ci-robot commented Apr 28, 2026

Uh oh!

igsilya commented Apr 30, 2026

Uh oh!

openshift-ci-robot commented Apr 30, 2026 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-merge-bot Bot commented Apr 30, 2026

Uh oh!

openshift-ci Bot commented Apr 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

11 participants

igsilya commented Mar 20, 2026 •

edited

Loading

openshift-ci-robot commented Mar 20, 2026 •

edited by openshift-ci Bot

Loading

coderabbitai Bot commented Mar 20, 2026 •

edited

Loading

openshift-ci-robot commented Apr 8, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Apr 28, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Apr 28, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci-robot commented Apr 30, 2026 •

edited by openshift-ci Bot

Loading