Mirantis OpenStack

Floating ip doesn't work after the live migration with DVR

Bug #1620863 reported by Eugene Nikanorov
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Released
High
Anton Chevychalov
Mirantis OpenStack 7.0-mu-6

Bug Description

Found on 7.0
See upstream bug: https://bugs.launchpad.net/neutron/+bug/1585165

Revision history for this message
Alexander Ignatov (aignatov) wrote :

Fix for it is here: https://review.fuel-infra.org/#/c/25774/

Changed in mos:
status: Confirmed → In Progress
milestone: none → 7.0-updates
Eugene Nikanorov (enikanorov)
Changed in mos:
milestone: 7.0-updates → 7.0-mu-6
tags: added: ct-patched
tags: added: ct-patched-7.0
removed: ct-patched
Anton Chevychalov (achevychalov)
Changed in mos:
assignee: Eugene Nikanorov (enikanorov) → Anton Chevychalov (achevychalov)
Denis Meltsaykin (dmeltsaykin)
Changed in mos:
status: In Progress → Fix Committed
TatyanaGladysheva (tgladysheva)
tags: added: on-verification
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Verified on MOS 7.0 + MU6 updates using steps from upstream bug.

Actual result:
Only one node that hosts VM after live migration answers the ARP request:
[root@nailgun ~]# arping -I eth1 10.109.8.131
ARPING 10.109.8.131 from 10.109.5.254 eth1
Unicast reply from 10.109.8.131 [FA:16:3E:B5:E1:FB] 580.287ms
Unicast reply from 10.109.8.131 [FA:16:3E:B5:E1:FB] 1.252ms
Unicast reply from 10.109.8.131 [FA:16:3E:B5:E1:FB] 1.182ms
Unicast reply from 10.109.8.131 [FA:16:3E:B5:E1:FB] 1.232ms
Unicast reply from 10.109.8.131 [FA:16:3E:B5:E1:FB] 1.064ms

There is no floatingip namespace on the compute that was hosting the VM before migration:

root@node-6:~# ip netns show
qrouter-252b7902-88b3-4a2f-9746-dc73b0ac3725

Floatingip namespace is located on the compute that it's hosting the VM after migration:

root@node-7:~# ip netns show
fip-d5a5b190-6ad0-4ea6-9298-c219d70785a7
qrouter-252b7902-88b3-4a2f-9746-dc73b0ac3725

root@node-7:~# ip netns exec fip-d5a5b190-6ad0-4ea6-9298-c219d70785a7 ip route
default via 10.109.8.1 dev fg-e5fb4634-53
10.109.8.0/24 dev fg-e5fb4634-53 proto kernel scope link src 10.109.8.133
10.109.8.131 via 169.254.31.28 dev fpr-252b7902-8
169.254.31.28/31 dev fpr-252b7902-8 proto kernel scope link src 169.254.31.29

tags: removed: on-verification
Changed in mos:
status: Fix Committed → Fix Released
TatyanaGladysheva (tgladysheva)
tags: added: on-automation
Revision history for this message
TatyanaGladysheva (tgladysheva) wrote :

Test case is automated: https://review.gerrithub.io/#/c/298141/

tags: added: covered-automated-test
removed: on-automation
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.