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

igsilya · 2026-03-20T11:36:02Z

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.el9fdp is the latest available version.

Manual cherry pick of the change from 4.14: #3073

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:36:07Z

@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.13.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.

Keeping OKD versions separate since sometimes new major versions are not released at the same time in FDP/RHEL and CentOS, so we may need them different at some point in time.

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.14: #3073

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:36:10Z

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: 2f360a96-b07c-40dd-98f7-c40664968244

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.}

openshift-ci-robot · 2026-03-20T11:42:51Z

@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.13.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.14: #3073

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

/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

openshift-ci · 2026-04-13T12:11:07Z

[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:30:23Z

/retest-required

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

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

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

/test gofmt

openshift-ci · 2026-04-15T11:19:22Z

@igsilya: The following test 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	`8a050dd`	link	false	`/test security`

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.

tssurya · 2026-04-20T17:26:18Z

/override ci/prow/gofmt

INFO[2026-04-15T11:19:07Z] Logs for container test in pod gofmt:        
INFO[2026-04-15T11:19:07Z] !!! 'gofmt -s' needs to be run on the following files: 
./pkg/cni/utils.go
./pkg/libovsdbops/db_object_ids.go
make: *** [Makefile:87: gofmt] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2026-04-15T11:19:07Z"} 
INFO[2026-04-15T11:19:07Z] Ran for 14m6s

GRR - we need a PR to fix this @taanyas can you please help ?

openshift-ci · 2026-04-20T17:30:35Z

@tssurya: Overrode contexts on behalf of tssurya: ci/prow/gofmt

Details

In response to this:

/override ci/prow/gofmt

INFO[2026-04-15T11:19:07Z] Logs for container test in pod gofmt:        
INFO[2026-04-15T11:19:07Z] !!! 'gofmt -s' needs to be run on the following files: 
./pkg/cni/utils.go
./pkg/libovsdbops/db_object_ids.go
make: *** [Makefile:87: gofmt] Error 1
{"component":"entrypoint","error":"wrapped process failed: exit status 2","file":"sigs.k8s.io/prow/pkg/entrypoint/run.go:84","func":"sigs.k8s.io/prow/pkg/entrypoint.Options.internalRun","level":"error","msg":"Error executing test process","severity":"error","time":"2026-04-15T11:19:07Z"} 
INFO[2026-04-15T11:19:07Z] Ran for 14m6s

GRR - we need a PR to fix this @taanyas can you please help ?

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.

igsilya · 2026-04-28T15:11:16Z

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

openshift-ci-robot · 2026-04-28T15:11:34Z

@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

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-28T15:51:41Z

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

release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.

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.13.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.el9fdp is the latest available version.

Manual cherry pick of the change from 4.14: #3073

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-28T15:52:46Z

/jira refresh

openshift-ci-robot · 2026-04-28T15:52:55Z

@igsilya: This pull request references Jira Issue OCPBUGS-84635, 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.13.z) matches configured target version for branch (4.13.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-78982 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-78982 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.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.13.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-ci-robot · 2026-04-28T15:56:25Z

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

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.el9fdp is the latest available version.

Manual cherry pick of the change from 4.14: #3073

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

openshift-merge-robot · 2026-04-30T01:47:25Z

Fix included in release 4.13.0-0.nightly-2026-04-29-175937

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 JacobTanenbaum and abhat March 20, 2026 11:36

igsilya mentioned this pull request Mar 20, 2026

OCPBUGS-84636, CORENET-6055: [release-4.12] Dockerfile: Unpin OVN and consume the latest from FDP #3075

Open

tssurya approved these changes 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, rbbratta, 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.13] CORENET-6055: ovn-kubernetes: Remove exemptions for now unpinned OVN rpms. openshift-eng/ocp-build-data#10061

Open

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

igsilya changed the title ~~CORENET-6055: [release-4.13] Dockerfile: Unpin OVN and consume the latest from FDP~~ OCPBUGS-84635, CORENET-6055: [release-4.13] 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

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 28, 2026

openshift-merge-bot Bot merged commit ad66078 into openshift:release-4.13 Apr 28, 2026
20 of 21 checks passed

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!

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!

tssurya left a comment

Choose a reason for hiding this comment

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!

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

Uh oh!

Uh oh!

tssurya commented Apr 20, 2026

Uh oh!

openshift-ci Bot commented Apr 20, 2026

Uh oh!

igsilya commented Apr 28, 2026

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 • edited by openshift-ci Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

openshift-ci-robot commented Apr 28, 2026

Uh oh!

openshift-merge-robot commented Apr 30, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

12 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 Mar 20, 2026 •

edited by openshift-ci Bot

Loading

openshift-ci Bot commented Apr 15, 2026 •

edited

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