Skip to content
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

[release-4.15] Upgrade openvswitch package version to 3.3 #4700

Open
wants to merge 1 commit into
base: release-4.15
Choose a base branch
from

Conversation

igsilya
Copy link
Contributor

@igsilya igsilya commented Mar 18, 2025

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

This change follows a corresponding move of RHCOS at openshift/os#1774 and OVN-Kubernetes at openshift/ovn-kubernetes#2492 to the same OVS 3.3. MicroShift should stay in sync.

The plan is to get this change to 4.15 once corresponding os and ovn-kubernetes PRs are in, and then backport to 4.14 when corresponding os and ovn-kubernetes PRs are backported.

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

This change follows a corresponding move of RHCOS and OVN-Kubernetes
to the same OVS 3.3.  MicroShift should stay in sync.

Signed-off-by: Ilya Maximets <[email protected]>
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 18, 2025
Copy link
Contributor

openshift-ci bot commented Mar 18, 2025

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@igsilya
Copy link
Contributor Author

igsilya commented Mar 18, 2025

/test all

Copy link
Contributor

openshift-ci bot commented Mar 18, 2025

[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 zshi-redhat for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@igsilya igsilya marked this pull request as ready for review March 18, 2025 19:06
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Mar 18, 2025
@openshift-ci openshift-ci bot requested review from pacevedom and pmtk March 18, 2025 19:07
@igsilya
Copy link
Contributor Author

igsilya commented Mar 18, 2025

/hold
Until corresponding openshift/os#1774 and openshift/ovn-kubernetes#2492 land.

CC: @zshi-redhat

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 18, 2025
@igsilya
Copy link
Contributor Author

igsilya commented Mar 18, 2025

/retest

@pmtk
Copy link
Member

pmtk commented Mar 21, 2025

Looks unrelated to the changes in the PR
/test microshift-metal-tests-arm

@pmtk
Copy link
Member

pmtk commented Mar 21, 2025

/test microshift-metal-tests-arm

1 similar comment
@pmtk
Copy link
Member

pmtk commented Mar 21, 2025

/test microshift-metal-tests-arm

Copy link
Contributor

openshift-ci bot commented Mar 21, 2025

@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/microshift-metal-tests-arm 656773e link true /test microshift-metal-tests-arm

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants