Bug 1494031

Summary: Connectivity issues after migrating an instance
Product: Red Hat OpenStack Reporter: Sahid Ferdjaoui <sferdjao>
Component: python-os-vifAssignee: Sahid Ferdjaoui <sferdjao>
Status: CLOSED ERRATA QA Contact: Gabriel Szasz <gszasz>
Severity: high Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: amuller, awaugama, berrange, bhaley, chhu, chrisw, dasmith, dgilbert, dyuan, eglynn, fcami, gkadam, jdenemar, jhakimra, jishao, jjoyce, jschluet, kchamart, knoel, lijin, lruzicka, lyarwood, mkalinin, molasaga, mst, nchandek, nlevinki, nyechiel, pablo.iranzo, panbalag, pmorey, saime, sbauza, sferdjao, sgordon, slinaber, srevivo, stephenfin, tvignaud, vaggarwa, vromanso, xuzhang, yafu, zpeng
Target Milestone: z6Keywords: Triaged, ZStream
Target Release: 10.0 (Newton)   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: python-os-vif-1.2.1-3.el7ost Doc Type: Bug Fix
Doc Text:
Originally, if an instance was migrated to a new location, the connection to the instance was broken, although the instance was successfully spawned in the new location. The connection was recreated after the original connection timed out. To workaround this issue, the linux bridge installed for the particular VIF type `ovs-hybrid` should be configured to persistently retain the MAC address learned from the RARP packets that are sent by QEMU (after starting on the destination node). This will avoid any disruption of the data-path during a live migration, since at some point during the process the live migration source and destination can be on the same L2 network, and could have the destination bridge learning from the source.
Story Points: ---
Clone Of: 1494030 Environment:
Last Closed: 2017-11-15 13:51:18 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, 1494030, 1494983    
Bug Blocks: 1381612    

Comment 10 errata-xmlrpc 2017-11-15 13:51:18 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:3230