Bug 1494031 - Connectivity issues after migrating an instance
Summary: Connectivity issues after migrating an instance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-os-vif
Version: 10.0 (Newton)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: z6
: 10.0 (Newton)
Assignee: Sahid Ferdjaoui
QA Contact: Gabriel Szasz
URL:
Whiteboard:
Depends On: 1440462 1494026 1494030 1494983
Blocks: 1381612
TreeView+ depends on / blocked
 
Reported: 2017-09-21 11:24 UTC by Sahid Ferdjaoui
Modified: 2022-08-16 12:34 UTC (History)
44 users (show)

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.
Clone Of: 1494030
Environment:
Last Closed: 2017-11-15 13:51:18 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 501132 0 'None' MERGED ovs-hybrid: should permanently keep MAC entries 2020-10-05 06:19:12 UTC
Red Hat Issue Tracker OSP-4701 0 None None None 2022-08-16 12:34:16 UTC
Red Hat Knowledge Base (Solution) 2993141 0 None None None 2017-09-21 11:24:44 UTC
Red Hat Product Errata RHBA-2017:3230 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 10 Bug Fix and Enhancement Advisory 2017-11-15 18:39:20 UTC

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
Note You need to log in before you can comment on or make changes to this bug.