Hide Forgot
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:
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.