OCPBUGS-74492, CORENET-6055: [release-4.17] Dockerfile: Unpin OVN and consume the latest from FDP

[igsilya]

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.

OVN-Kubernetes is currently using the latest OVN builds already, so this PR doesn't actually change anything for the current images. But it will bring newer OVN builds automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.18: #2895

[openshift-ci-robot]

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

OVN-Kubernetes is currently using the latest OVN builds already, so this PR doesn't actually change anything for the current images. But it will bring newer OVN builds automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.18: #2895

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]

/jira cherry-pick OCPBUGS-66428

[openshift-ci-robot]

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

Details

In response to this:

/jira cherry-pick OCPBUGS-66428

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]

@igsilya: This pull request references Jira Issue OCPBUGS-74492, 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.17.z) matches configured target version for branch (4.17.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-66428 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-66428 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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.

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.

OVN-Kubernetes is currently using the latest OVN builds already, so this PR doesn't actually change anything for the current images. But it will bring newer OVN builds automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.18: #2895

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]

@igsilya: This pull request references Jira Issue OCPBUGS-74492, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.z) matches configured target version for branch (4.17.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-66428 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-66428 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

OVN-Kubernetes is currently using the latest OVN builds already, so this PR doesn't actually change anything for the current images. But it will bring newer OVN builds automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.18: #2895

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]

/jira refresh

[openshift-ci-robot]

@igsilya: This pull request references Jira Issue OCPBUGS-74492, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.17.z) matches configured target version for branch (4.17.z)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-66428 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-66428 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
• bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

[igsilya]

Half the jobs failed to fetch existing microshift image for some reason.
/retest

[igsilya]

Timed out installing unrelated RPMs...
/retest

[igsilya]

GCP infra provisioning issues, windows didn't pass for a very long time.
/retest-required

[igsilya]

/test e2e-gcp-ovn-techpreview

[openshift-ci]

@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	039a0e1	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.

[igsilya]

Let's try one more time. For some reason the node rediness checks expects 6 nodes, but there are only 5...
/test e2e-gcp-ovn-techpreview

[ricky-rav]

/LGTM
/approve

[ricky-rav]

/label backport-risk-assessed
/override ci/prow/e2e-aws-ovn-windows
/verified by ci

[openshift-ci-robot]

@ricky-rav: This PR has been marked as verified by ci.

Details

In response to this:

/label backport-risk-assessed
/override ci/prow/e2e-aws-ovn-windows
/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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: igsilya, ricky-rav

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 [ricky-rav]

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

[openshift-ci]

@ricky-rav: Overrode contexts on behalf of ricky-rav: ci/prow/e2e-aws-ovn-windows

Details

In response to this:

/label backport-risk-assessed
/override ci/prow/e2e-aws-ovn-windows
/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 kubernetes-sigs/prow repository.

[ricky-rav]

/label backport-risk-assessed label

[ricky-rav]

/label backport-risk-assessed

[openshift-ci-robot]

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

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.

OVN-Kubernetes is currently using the latest OVN builds already, so this PR doesn't actually change anything for the current images. But it will bring newer OVN builds automatically as soon as they are released in the future. Major version upgrades still require a separate PR.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.18: #2895

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]

/cherrypick release-4.16

[openshift-cherrypick-robot]

@igsilya: #2959 failed to apply on top of branch "release-4.16":

Applying: Dockerfile: Unpin OVN and consume the latest from FDP.
Using index info to reconstruct a base tree...
M	Dockerfile.base
Falling back to patching base and 3-way merge...
Auto-merging Dockerfile.base
CONFLICT (content): Merge conflict in Dockerfile.base
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 Dockerfile: Unpin OVN and consume the latest from FDP.

Details

In response to this:

/cherrypick release-4.16

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-robot]

Fix included in accepted release 4.17.0-0.nightly-2026-02-06-091352