Bug 1323694

Summary: Floating IP not accessible after forcing qrouter failover
Product: Red Hat OpenStack Reporter: Robin Cernin <rcernin>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED WORKSFORME QA Contact: Toni Freger <tfreger>
Severity: high Docs Contact:
Priority: medium    
Version: 7.0 (Kilo)CC: amuller, chrisw, ealcaniz, felipe.alfaro, nyechiel, rcernin, srevivo
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-06-05 14:02:24 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:
Bug Depends On:    
Bug Blocks: 1339488    

Description Robin Cernin 2016-04-04 12:58:48 UTC 
Description of problem:

Forcing failover of controller which currently hosts qrouter by shutting it down to move qrouter to another node, causes that some floating IP addresses of qrouter stops working.


Version-Release number of selected component (if applicable):

 OSP 7.3.1.

openstack-neutron-2015.1.2-11.el7ost.noarch
openstack-neutron-bigswitch-lldp-2015.1.38-1.el7ost.noarch
openstack-neutron-common-2015.1.2-11.el7ost.noarch
openstack-neutron-lbaas-2015.1.2-1.el7ost.noarch
openstack-neutron-metering-agent-2015.1.2-11.el7ost.noarch
openstack-neutron-ml2-2015.1.2-11.el7ost.noarch
openstack-neutron-openvswitch-2015.1.2-11.el7ost.noarch
python-neutron-2015.1.2-11.el7ost.noarch
python-neutron-lbaas-2015.1.2-1.el7ost.noarch
python-neutronclient-2.4.0-2.el7ost.noarch


How reproducible:


Steps to Reproduce:
1. Neutron l3-agent-list-hosting-router qrouter
2. Perform shutdown of controller with active L3 agent
3.

Actual results:
Some of the floating IP addresses of qrouter stops working.

Expected results:
All floating IP addresses of qrouter are working.

Additional info:
Comment 6 Assaf Muller 2016-06-04 16:14:57 UTC 
I see that the case was closed. Still relevant?

Looking at the information in the RHBZ, some IPv4 addresses on the 'qg' device can be pinged, some cannot, it sounds very bizarre. It looks like a lower level issue than Neutron.

One thing I would check is if a GARP for each IP on the 'qg' device was sent out from the qrouter namespace before the pings were issued.