Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

The FDP team is no longer accepting new bugs in Bugzilla. Please report your issues under FDP project in Jira. Thanks.

Bug 1843811

Summary:	[OVN] Update of OVN to 2.13.0-28 causing ovn-controller br-int connection failures due required OpenFlow 1.5
Product:	Red Hat Enterprise Linux Fast Datapath	Reporter:	Maciej Józefczyk <mjozefcz>
Component:	ovn2.13	Assignee:	OVN Team <ovnteam>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ehsan Elahi <eelahi>
Severity:	high	Docs Contact:
Priority:	high
Version:	FDP 20.D	CC:	ctrautma, dalvarez, jishi, jlibosva, kforde, mmichels, nusiddiq, ralongi
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 10:59:06 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:	1782834
Bug Blocks:

Description Maciej Józefczyk 2020-06-04 08:22:18 UTC

Description of problem:
It was noticed during PerfScale testing on OSP16 deployment.

During manual upgrade of OVN from 2.11 to manually build package from branch 20.06, the ovn-controllers can't connect to previously created bridges, like br-int, because of lack of support for Openflow 1.5 on bridge.

Example error found on ovn-controller logs:
2020-06-03T13:55:20.204Z|00086|rconn|WARN|unix:/var/run/openvswitch/br-int.mgmt: connection dropped (Protocol error)

Bridge was previously created with protocols=[].

After executing:
"ovs-vsctl set bridge br-int protocols=OpenFlow13,OpenFlow15"

OVN-controller is able to connect to the bridge.

How reproducible:


Steps to Reproduce:
1. Install OVN with 2.11
2. Create br-int
3. Upgrade OVN to 20.06

Actual results:
ovn-controller can't connect to br-int

Expected results:
ovn-controller should connect to br-int

Comment 4 Numan Siddique 2020-07-20 07:00:45 UTC

Possible workaround is to add the protocol OpenFlow15 to the protocols column of br-int - ovs-vsctl add bridge br-int protocols OpenFlow15

or

clear the protocols colum - "ovs-vsctl clear bridge br-int protocols"

Comment 5 Jakub Libosvar 2020-07-30 15:47:53 UTC

(In reply to Numan Siddique from comment #4)
> Possible workaround is to add the protocol OpenFlow15 to the protocols
> column of br-int - ovs-vsctl add bridge br-int protocols OpenFlow15
> 
> or
> 
> clear the protocols colum - "ovs-vsctl clear bridge br-int protocols"

Neither help because of bug 1782834

Comment 6 Jakub Libosvar 2020-08-05 10:47:43 UTC

Worth to note this happens only when updating OVN to 2.13 while having OVS 2.11. 

 - OVS 2.11 by default supports OF protocols up to 1.4, and OVN 2.13 connects with OF protocol 1.5. 
 - OVS 2.13 by default supports OF protocols up to 1.5, so OVN 2.13 has no issues connecting to the integration bridge
 - OVS 2.11 doesn't contain the regression described in 1782834 so the workarounds specified in comment 4 should work.