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

Bug 1942449

Summary:	FFWD2 13->16 ovn db possible data loss during ffwd
Product:	Red Hat OpenStack	Reporter:	Lukas Bezdicka <lbezdick>
Component:	openstack-tripleo-heat-templates	Assignee:	Lukas Bezdicka <lbezdick>
Status:	CLOSED ERRATA	QA Contact:	Khomesh Thakre <kthakre>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	16.1 (Train)	CC:	jfrancoa, jlibosva, jpretori, kthakre, mburns, sgolovat
Target Milestone:	z3	Keywords:	Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.6.1-2.20220123005237.a2533dd.el8ost	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-06-22 16:02:30 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 Lukas Bezdicka 2021-03-24 12:04:56 UTC

Ovn database master is not copied to the first leapped node which can end up with loss of data about changes that happens during first 1/3rd of controlplane upgrade.

Comment 3 Lukas Bezdicka 2021-12-01 12:44:11 UTC

Confirmed.

Steps to reproduce:
1) System upgrade controller-0 but don't continue with upgrade.
2) Spawn few vms and start pinging them - this creates records on ctrl1 and ctrl2
3) Continue with upgrade where ctrl1 and ctrl2 are shut off and ctrl0 deploys
4) During deployment when ovndb* starts on ctrl0 the ping starts to fail.

I verified that both ctrl1 and ctrl2 ovnsb/nb dbs can be copied and resolve the issue.

Comment 5 Sergii Golovatiuk 2021-12-14 12:56:20 UTC

*** Bug 2028164 has been marked as a duplicate of this bug. ***

Comment 6 Lukas Bezdicka 2022-02-23 14:20:59 UTC

Patch is part of 16.2-trunk-patches.

Comment 15 errata-xmlrpc 2022-06-22 16:02:30 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 (Release of components for Red Hat OpenStack Platform 16.2.3 (Train)), 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/RHBA-2022:4793