OCPBUGS-55951: Bump ovn and ovs to latest 23.06 and 3.1 respectively

[sdodson]

This moves ovs from 2.17 in the container image to 3.1 matching RHCOS as used since Feb 2024, see https://issues.redhat.com/browse/OCPBUGS-22701

Regression testing only, no specific functional fixes

[openshift-ci-robot]

@sdodson: This pull request references Jira Issue OCPBUGS-55951, which is invalid:

• expected the bug to target either version "4.12." or "openshift-4.12.", but it targets "4.13.z" instead
• 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.
• expected Jira Issue OCPBUGS-55951 to depend on a bug targeting a version in 4.13.0, 4.13.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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 moves ovs from 2.17 in the container image to 3.1 matching RHCOS as used since Feb 2024, see https://issues.redhat.com/browse/OCPBUGS-22701

Regression testing only, no specific functional fixes

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: sdodson
Once this PR has been reviewed and has the lgtm label, please assign jacobtanenbaum 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:

• OWNERS

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

[sdodson]

/retest-required

[tssurya]

@igsilya : can you PTAL this? what are the OVS side implications here? What are the new things we are bringing in?
@asood-rh and @anuragthehatter PTAL

[tssurya]

/retest-required

[igsilya]

@igsilya : can you PTAL this? what are the OVS side implications here? What are the new things we are bringing in?

@tssurya Mostly the same stuff as in here: #2553 (comment)
Since we're upgrading from 2.17 to 3.1, we're also gaining a few performance improvements in OVSDB. The most important one is the move of the database compaction processing into a separate thread.

No major API changes that we'd care about inside the container.

[sdodson]

/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade

[tssurya]

/retest-required
holding approval for green CI

[sdodson]

/override ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade ci/prow/4.12-upgrade-from-stable-4.11-local-gateway-e2e-aws-ovn-upgrade

Neither of those have passed since February

[openshift-ci]

@sdodson: Overrode contexts on behalf of sdodson: ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade, ci/prow/4.12-upgrade-from-stable-4.11-local-gateway-e2e-aws-ovn-upgrade

In response to this:

/override ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade ci/prow/4.12-upgrade-from-stable-4.11-local-gateway-e2e-aws-ovn-upgrade

Neither of those have passed since February

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

@sdodson: 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/security	11d0867	link	false	/test security
ci/prow/e2e-azure-ovn	11d0867	link	false	/test e2e-azure-ovn
ci/prow/e2e-aws-ovn-hypershift	11d0867	link	false	/test e2e-aws-ovn-hypershift

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.