Skip to content

[release-4.14] OCPBUGS-54732: Dockerfile.base: bump OVS version to 3.3 #2511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2492

/assign igsilya

Open vSwitch 3.1 is EoL upstream and so the support of this version
in FDP is limited.  To ensure timely bug fix delivery for OCP 4.14+ we
need to upgrade to the current LTS stream, which is Open vSwitch 3.3.
It will be fully supported for much longer.

Consolidation of versions used across releases of OpenShift will also
reduce pressure on QE teams allowing to drop older releases not used
by any products.

We're moving RHCOS to this version as well, and we should keep the
versions in the container and on the host in sync.  The exact build in
this commit is the one that is currently used in OCP 4.16.

Signed-off-by: Ilya Maximets <[email protected]>
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-53384 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-4.14] OCPBUGS-54732: Dockerfile.base: bump OVS version to 3.3

In response to this:

This is an automated cherry-pick of #2492

/assign igsilya

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 openshift-ci bot changed the title [release-4.14] OCPBUGS-53384: Dockerfile.base: bump OVS version to 3.3 [release-4.14] OCPBUGS-54732: Dockerfile.base: bump OVS version to 3.3 Apr 8, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 8, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-54732, which is invalid:

  • expected dependent Jira Issue OCPBUGS-53384 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.

In response to this:

This is an automated cherry-pick of #2492

/assign igsilya

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 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 8, 2025
@igsilya
Copy link
Contributor

igsilya commented Apr 9, 2025

/retest

@igsilya
Copy link
Contributor

igsilya commented Apr 9, 2025

/jira refresh

@openshift-ci-robot 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 9, 2025
@openshift-ci-robot
Copy link
Contributor

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-53384 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-53384 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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 openshift-ci bot requested a review from anuragthehatter April 9, 2025 21:27
@igsilya
Copy link
Contributor

igsilya commented Apr 9, 2025

/retest-required

Copy link
Contributor

@igsilya igsilya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a clean cherry-pick, so
/lgtm
/retest

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 11, 2025
@sdodson
Copy link
Member

sdodson commented Apr 23, 2025

/approved
/label backport-risk-assessed

@openshift-ci 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 23, 2025
@zshi-redhat
Copy link
Contributor

/test e2e-aws-ovn-fdp-qe

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@zshi-redhat: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test 4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade
/test 4.14-upgrade-from-stable-4.13-images
/test 4.14-upgrade-from-stable-4.13-local-gateway-e2e-aws-ovn-upgrade
/test 4.14-upgrade-from-stable-4.13-local-gateway-images
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-local-gateway
/test e2e-aws-ovn-local-to-shared-gateway-mode-migration
/test e2e-aws-ovn-serial
/test e2e-aws-ovn-shared-to-local-gateway-mode-migration
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-local-gateway
/test e2e-aws-ovn-windows
/test e2e-gcp-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-ipv6
/test gofmt
/test images
/test lint
/test unit

The following commands are available to trigger optional jobs:

/test e2e-aws-ovn-clusternetwork-cidr-expansion
/test e2e-aws-ovn-kubevirt
/test e2e-azure-ovn
/test e2e-metal-ipi-ovn-ipv4
/test e2e-openstack-ovn
/test e2e-ovn-hybrid-step-registry
/test e2e-vsphere-ovn
/test e2e-vsphere-windows
/test qe-perfscale-aws-ovn-medium-cluster-density
/test qe-perfscale-aws-ovn-medium-node-density-cni
/test qe-perfscale-aws-ovn-small-cluster-density
/test qe-perfscale-aws-ovn-small-node-density-cni
/test security

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-ovn-kubernetes-release-4.14-4.14-upgrade-from-stable-4.13-e2e-aws-ovn-upgrade
pull-ci-openshift-ovn-kubernetes-release-4.14-4.14-upgrade-from-stable-4.13-images
pull-ci-openshift-ovn-kubernetes-release-4.14-4.14-upgrade-from-stable-4.13-local-gateway-e2e-aws-ovn-upgrade
pull-ci-openshift-ovn-kubernetes-release-4.14-4.14-upgrade-from-stable-4.13-local-gateway-images
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-hypershift
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-kubevirt
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-local-gateway
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-local-to-shared-gateway-mode-migration
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-serial
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-shared-to-local-gateway-mode-migration
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-upgrade
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-upgrade-local-gateway
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-windows
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-azure-ovn
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-gcp-ovn
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-openstack-ovn
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-ovn-hybrid-step-registry
pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-vsphere-ovn
pull-ci-openshift-ovn-kubernetes-release-4.14-gofmt
pull-ci-openshift-ovn-kubernetes-release-4.14-images
pull-ci-openshift-ovn-kubernetes-release-4.14-lint
pull-ci-openshift-ovn-kubernetes-release-4.14-security
pull-ci-openshift-ovn-kubernetes-release-4.14-unit

In response to this:

/test e2e-aws-ovn-fdp-qe

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.

@asood-rh
Copy link

asood-rh commented Apr 23, 2025

/test e2e-aws-ovn-fdp-qe

@zshi-redhat The workflow is only available in 4.16 onwards.
The OVN test cases were executed and results are added in comments in #2455

We can test this PR in similar fashion.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 23, 2025
Copy link
Contributor

@igsilya igsilya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Still good after rebase.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 23, 2025
@asood-rh
Copy link

asood-rh commented Apr 23, 2025

Ginkgo Test Results

04-23 16:49:18.894  Writing JUnit report to junit_e2e_20250423-204913.xml
04-23 16:49:18.894  
04-23 16:49:18.894  36 pass, 3 skip (1h35m10s)
04-23 16:49:18.894  junit_e2e_20250423-204913.xml
04-23 16:49:18.894  isJenkinsEnv: True\n

Cucushift

31 scenarios (2 skipped, 29 passed)
1217 steps (46 skipped, 1171 passed)
35m24.031s

@asood-rh
Copy link

/label qe-approved

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Apr 23, 2025
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-54732, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.z) matches configured target version for branch (4.14.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-53384 is in the state Closed (Done-Errata), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-53384 targets the "4.15.z" version, which is one of the valid target versions: 4.15.0, 4.15.z
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

This is an automated cherry-pick of #2492

/assign igsilya

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.

@asood-rh
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 23, 2025
@sdodson sdodson added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 23, 2025
Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: igsilya, openshift-cherrypick-robot

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@sdodson
Copy link
Member

sdodson commented Apr 23, 2025

/override ci/prow/e2e-aws-ovn-upgrade
This passed before this was rebase atop a more recent commit

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/e2e-aws-ovn-upgrade

In response to this:

/override ci/prow/e2e-aws-ovn-upgrade
This passed before this was rebase atop a more recent commit

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.

@sdodson
Copy link
Member

sdodson commented Apr 23, 2025

/override ci/prow/e2e-aws-ovn-windows
Same

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

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

In response to this:

/override ci/prow/e2e-aws-ovn-windows
Same

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.

Copy link
Contributor

openshift-ci bot commented Apr 23, 2025

@openshift-cherrypick-robot: 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/e2e-aws-ovn-windows a4c0d06 link true /test e2e-aws-ovn-windows
ci/prow/e2e-aws-ovn-upgrade a4c0d06 link true /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-kubevirt a4c0d06 link false /test e2e-aws-ovn-kubevirt
ci/prow/security a4c0d06 link false /test security

Full PR test history. Your PR dashboard.

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-merge-bot openshift-merge-bot bot merged commit 51b4e0f into openshift:release-4.14 Apr 23, 2025
25 of 27 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-54732: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be 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-54732 has not been moved to the MODIFIED state.

In response to this:

This is an automated cherry-pick of #2492

/assign igsilya

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-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-base
This PR has been included in build ose-ovn-kubernetes-base-container-v4.14.0-202504232336.p0.g51b4e0f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ovn-kubernetes-microshift
This PR has been included in build ovn-kubernetes-microshift-container-v4.14.0-202504232336.p0.g51b4e0f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: ose-ovn-kubernetes
This PR has been included in build ose-ovn-kubernetes-container-v4.14.0-202504232336.p0.g51b4e0f.assembly.stream.el9.
All builds following this will include this PR.

@openshift-merge-robot
Copy link
Contributor

Fix included in accepted release 4.14.0-0.nightly-2025-04-24-012548

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.