Open Stack

On 03/21/2018 05:38 PM, Mārtiņš Jakubovičs wrote:
> Hello Brian,
> 
> Yes, after migration it works well, but during migration it is not.

Ok, so somehow neutron is configuring things too early, updating the 
floating IP (and your ARP cache), before the instance has finished 
migration.  It would be good if you could look at the nova and neutron 
logs to help piece this together - i.e. when is nova telling neutron to 
configure the migrated port, etc.

Also, without looking at what's changed since Newton, trying a live 
migration on plain Ocata (or Pike) would be a good data point, just in 
case there was a bug somewhere that is now fixed.

Thanks,

-Brian

> On 2018.03.21. 23:37, Brian Haley wrote:
>> On 03/21/2018 04:52 PM, Mārtiņš Jakubovičs wrote:
>>> Dear all,
>>>
>>> I faced issue when migrating instance by live-migration + 
>>> block-migration guests floating IP became inaccessible. My setup are 
>>> OVS + DVR. Currently upgrading from Newton to Ocata.
>>>
>>> Looks like when migration starts, in destination host neutron 
>>> configures floating IP so traffic start to go to destination host but 
>>> instance are still in source host.
>>>
>>> Does live migration work correctly with DVR?
>>
>> It should.  Does the floating IP work after migration is finished?  Is 
>> it just temporary?
>>
>> -Brian
>>
>