OCPBUGS-76403, CORENET-6055: [release-4.15] 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.

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.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

[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.15.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.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

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-76277

[openshift-ci-robot]

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

Details

In response to this:

/jira cherry-pick OCPBUGS-76277

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-76403, which is invalid:

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

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.

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

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 NOT APPROVED

This pull-request has been approved by: igsilya
Once this PR has been reviewed and has the lgtm label, please assign abhat for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[igsilya]

/retitle OCPBUGS-76403, CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP

[igsilya]

/retitle OCPBUGS-76403, CORENET-6055: [release-4.15] Dockerfile: Unpin OVN and consume the latest from FDP

[openshift-ci-robot]

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

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

(cherry picked from commit 3771a89)

Manual cherry pick of the change from 4.16: #2972

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]

/retest-required

[openshift-ci]

@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/lint	37686e1	link	true	/test lint
ci/prow/security	37686e1	link	false	/test security
ci/prow/gofmt	37686e1	link	true	/test gofmt
ci/prow/unit	37686e1	link	true	/test unit

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]

All passed on re-run. The gofmt/lint/unit jobs seem borked, and will need an override, AFAIU.

[igsilya]

/jira refresh

[openshift-ci-robot]

@igsilya: This pull request references Jira Issue OCPBUGS-76403, 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.15.z) matches configured target version for branch (4.15.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-76277 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-76277 targets the "4.16.z" version, which is one of the valid target versions: 4.16.0, 4.16.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.15.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.