Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1812882

Summary: Neutron regression: DVR no longer sends GARPs after instance's live migration
Product: Red Hat OpenStack Reporter: Alex Stupnikov <astupnik>
Component: openstack-neutronAssignee: Rodolfo Alonso <ralonsoh>
Status: CLOSED ERRATA QA Contact: Candido Campos <ccamposr>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 13.0 (Queens)CC: akatz, alfons.scheerer, amuller, chrisw, ekuris, jlibosva, ralonsoh, scohen
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: openstack-neutron-12.1.1-11.el7ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-06-24 11:53:08 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:

Description Alex Stupnikov 2020-03-12 12:36:00 UTC
Description of problem:

Customer reported a problem he faced with latest neutron docker images: VM's FIP become unreachable after live migration. We have isolated the problem to GARP for FIPs not being send after live migration. The problem was fixed after downgrading neutron docker images to much older version (so it is hard to isolate the moment when regression was introduced).

I have reproduced the problem in my lab (FIP: 10.0.0.213):

- GARPs are sent after FIP is associated [1]
- GARPs are not sent after live migration [2]
- GARPs are sent after regular migration [3]


Version-Release number of selected component (if applicable): latest neutron packages are affected

[root@controller-0 ~]# docker exec -it neutron_l3_agent rpm -qa | grep neutron
python-neutron-12.1.1-6.el7ost.noarch
python-neutron-lbaas-12.0.1-0.20190803015156.b86fcef.el7ost.noarch
python2-neutron-lib-1.13.0-2.el7ost.noarch
openstack-neutron-common-12.1.1-6.el7ost.noarch
python-neutron-fwaas-12.0.2-1.el7ost.noarch
openstack-neutron-lbaas-12.0.1-0.20190803015156.b86fcef.el7ost.noarch
openstack-neutron-ml2-12.1.1-6.el7ost.noarch
python2-neutronclient-6.7.0-1.el7ost.noarch
puppet-neutron-12.4.1-10.el7ost.noarch
openstack-neutron-12.1.1-6.el7ost.noarch
openstack-neutron-fwaas-12.0.2-1.el7ost.noarch


How reproducible:

Live-migrate instance with FIP in environment with DVR. Monitor GARPs.


[1]
  07:56:24.073266 ARP, Request who-has 10.0.0.213 (ff:ff:ff:ff:ff:ff) tell 10.0.0.213, length 28
  07:56:24.111287 ARP, Reply 10.0.0.213 is-at fa:16:3e:83:98:ea, length 28
  07:56:26.143161 ARP, Request who-has 10.0.0.213 (ff:ff:ff:ff:ff:ff) tell 10.0.0.213, length 28
  07:56:26.174079 ARP, Reply 10.0.0.213 is-at fa:16:3e:83:98:ea, length 28
  07:56:28.209436 ARP, Request who-has 10.0.0.213 (ff:ff:ff:ff:ff:ff) tell 10.0.0.213, length 28
  07:56:28.244115 ARP, Reply 10.0.0.213 is-at fa:16:3e:83:98:ea, length 28

[2]
NOTE. 10.0.0.211 is associated with L3 agent gateway on target compute node.

  07:59:28.862583 ARP, Request who-has 10.0.0.211 (ff:ff:ff:ff:ff:ff) tell 10.0.0.211, length 28
  07:59:28.900435 ARP, Reply 10.0.0.211 is-at fa:16:3e:66:6d:92, length 28
  07:59:30.932178 ARP, Request who-has 10.0.0.211 (ff:ff:ff:ff:ff:ff) tell 10.0.0.211, length 28
  07:59:30.979299 ARP, Reply 10.0.0.211 is-at fa:16:3e:66:6d:92, length 28

[3]
  08:10:50.751903 ARP, Request who-has 10.0.0.219 (ff:ff:ff:ff:ff:ff) tell 10.0.0.219, length 28
  08:10:50.813980 ARP, Reply 10.0.0.219 is-at fa:16:3e:83:98:ea, length 28
  08:10:51.432849 ARP, Request who-has 10.0.0.213 (ff:ff:ff:ff:ff:ff) tell 10.0.0.213, length 28
  08:10:51.467688 ARP, Reply 10.0.0.213 is-at fa:16:3e:83:98:ea, length 28
  08:10:52.847693 ARP, Request who-has 10.0.0.219 (ff:ff:ff:ff:ff:ff) tell 10.0.0.219, length 28
  08:10:52.881707 ARP, Reply 10.0.0.219 is-at fa:16:3e:83:98:ea, length 28
  08:10:53.505638 ARP, Request who-has 10.0.0.213 (ff:ff:ff:ff:ff:ff) tell 10.0.0.213, length 28
  08:10:53.538638 ARP, Reply 10.0.0.213 is-at fa:16:3e:83:98:ea, length 28
  08:10:54.923757 ARP, Request who-has 10.0.0.219 (ff:ff:ff:ff:ff:ff) tell 10.0.0.219, length 28
  08:10:54.955517 ARP, Reply 10.0.0.219 is-at fa:16:3e:83:98:ea, length 28
  08:10:55.580609 ARP, Request who-has 10.0.0.213 (ff:ff:ff:ff:ff:ff) tell 10.0.0.213, length 28
  08:10:55.612507 ARP, Reply 10.0.0.213 is-at fa:16:3e:83:98:ea, length 28

Comment 26 errata-xmlrpc 2020-06-24 11:53:08 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-2020:2724