Bug 2076719

Summary:	update to use openvswitch2.17
Product:	Red Hat OpenStack	Reporter:	Jon Schlueter <jschluet>
Component:	rhosp-openvswitch	Assignee:	Terry Wilson <twilson>
Status:	CLOSED NEXTRELEASE	QA Contact:	OSP Team <rhos-maint>
Severity:	high	Docs Contact:
Priority:	high
Version:	17.0 (Wallaby)	CC:	apevec, averdagu, dalvarez, mburns, twilson
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rhosp-openvswitch-2.17-5.el9osttrunk	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-05-31 21:40:24 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2076450, 2077165, 2077246
Bug Blocks:

Description Jon Schlueter 2022-04-19 18:17:23 UTC

Description of problem:

FDP 2.17 is requested to be used for OSP 17

rhosp-openstack will need to be updated to point to the updated package that will be available.

It also appears the network-scripts-openvswitch2.17 is not present.

This will need to be verified and updated accordingly.

Comment 1 Jon Schlueter 2022-04-19 18:43:58 UTC

bug 2076450 was filed after an initial attempt to update 2.17

Comment 2 Alan Pevec 2022-04-20 22:39:18 UTC

Copying from Terry's email on fd-lp and adding blockers for updating to OVS 2.17:

>> As we're planning to support OVN RAFT in 17, we definitely need a compose with OVS 2.17 which includes the necessary python-ovs code to enable this.

In addition to waiting on OVS 2.17 for python-ovs RAFT support, it's also been found that the patch that added RAFT support to python-ovs actually breaks Neutron and ovsdbapp's use of what was assumed to be an internal API (but was not marked as such by a leading underscore).

Neutron *will not start* with the OVS 2.17 as-is.

There is a patch in upstream ovs to restore backward compatibility [1] which will not make it before our downstream 2.17 GA FDP release. There are workarounds upstream for Neutron [2] and ovdbapp [3], and a stable/wallaby release of ovsdbapp [4] that needs to be merged. Once the upstream ovsdbapp release is made, we need to import that downstream and then we can merge the upstream stable/wallaby neutron patch and merge it downstream as well. Then everything should be fine.

I have created ovsdbapp [5], Neutron [6], and ovs [7] BZs to track that this is all done.

[1] https://patchwork.ozlabs.org/project/openvswitch/patch/20220413135226.593135-1-twilson@redhat.com/
[2] https://review.opendev.org/c/openstack/neutron/+/838784
[3] https://review.opendev.org/c/openstack/ovsdbapp/+/834729
[4] https://review.opendev.org/c/openstack/releases/+/838517
[5] https://bugzilla.redhat.com/show_bug.cgi?id=2077165
[6] https://bugzilla.redhat.com/show_bug.cgi?id=2077246
[7] https://bugzilla.redhat.com/show_bug.cgi?id=2077265

Comment 3 Terry Wilson 2022-05-02 13:25:55 UTC

There is another ovs patch needed to fix another backward compatibility edge case: https://patchwork.ozlabs.org/project/openvswitch/patch/20220430200952.863496-1-twilson@redhat.com/ (which is going to be updated soon to remove usage of python f-string because it isn't supported in py 3.5 which ubuntu 16.04 uses).