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

Bug 1885212

Summary:	[FFU][ovn] ovn-controllers can't connect to SB DB in hybrid state
Product:	Red Hat OpenStack	Reporter:	Jakub Libosvar <jlibosva>
Component:	openstack-tripleo-heat-templates	Assignee:	Lukas Bezdicka <lbezdick>
Status:	CLOSED ERRATA	QA Contact:	Jesse Pretorius <jpretori>
Severity:	high	Docs Contact:
Priority:	high
Version:	16.1 (Train)	CC:	apevec, fpantano, jpretori, lbezdick, lhh, majopela, mburns, scohen
Target Milestone:	z3	Keywords:	Triaged
Target Release:	16.1 (Train on RHEL 8.2)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.3.2-1.20200914170164.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-12-15 18:37:08 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:

Description Jakub Libosvar 2020-10-05 12:51:39 UTC

Description of problem:
When running FFU from 13 to 16, OVN databases are upgraded to OVN 2.13 on the running controller node. Compute nodes are left on OSP13 with OVN 2.11. That means ovn-controller running on a compute node is 2.11 talking to OVN 2.13 southbound database. The old ovn controller doesn't understand some of the new logical flows from the southbound DB.

We need to workaround it by upgrading ovn-controller on all compute nodes first.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 18 errata-xmlrpc 2020-12-15 18:37:08 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Red Hat OpenStack Platform 16.1.3 bug fix and enhancement advisory), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:5413