Bug 1494030

Summary:	Connectivity issues after migrating an instance
Product:	Red Hat OpenStack	Reporter:	Sahid Ferdjaoui <sferdjao>
Component:	python-os-vif	Assignee:	Sahid Ferdjaoui <sferdjao>
Status:	CLOSED ERRATA	QA Contact:	Gabriel Szasz <gszasz>
Severity:	high	Docs Contact:
Priority:	high
Version:	11.0 (Ocata)	CC:	amuller, awaugama, berrange, bhaley, chhu, chrisw, dasmith, dgilbert, dyuan, eglynn, fcami, gkadam, jdenemar, jhakimra, jishao, jjoyce, jschluet, kchamart, knoel, lijin, lyarwood, mkalinin, molasaga, mst, nchandek, nyechiel, panbalag, pmorey, saime, samccann, sbauza, sferdjao, sgordon, slinaber, srevivo, stephenfin, tvignaud, vaggarwa, vromanso, xuzhang, yafu, zpeng
Target Milestone:	z3	Keywords:	Triaged, ZStream
Target Release:	11.0 (Ocata)
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	python-os-vif-1.4.1-2.el7ost	Doc Type:	Bug Fix
Doc Text:	At some point during a live-migration, the source and destination bridges can be on the same L2 and we could have the destination bridge learning from the source bridge. To prevent this, configure the linux bridge installed for the particular vif type 'ovs-hybrid' to persistently keep the MAC learned from the RARP packets sent by QEMU when starting on destination node. This avoids any break of the datapath during a live-migration.	Story Points:	---
Clone Of:	1494026
Clones:	1494031 (view as bug list)		Environment:
Last Closed:	2017-10-31 17:40:41 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:	1440462, 1494026, 1494983
Bug Blocks:	1381612, 1494031

Comment 5 errata-xmlrpc 2017-10-31 17:40:41 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, 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-2017:3097