Description of problem: L3 Network Drops - Floating IP's are not Accessible Even if neutron services are restarted on management node, floating IP's are not accessible. Tenants need to restart their instances and then things work. Need to determine cause of initial l3 outage. Appears to be an upstream BZ noted here https://bugs.launchpad.net/neutron/+bug/1175695 Version-Release number of selected component (if applicable): current RHOS 4
The upstream bug looks like the probably cause. The next step is cherry-picking the fix for inclusion in stable/havana and figuring out if we can rely on the next sync or we need to manually backport to RHOS.
I Have tested on Havana A3 using distributed system openstack-neutron-2013.2.2-5.el6ost.noarch 1. I have stopped L3 agent 2. qrouter namespace is still up, and traffic to floating ip works 3. while starting L3 agent traffic stops for ~ 25 seconds and resume later [root@puma05 ~]# ip netns | grep qrouter qrouter-69cf3535-2960-4b11-8e3a-da37c3331f01 [root@puma05 ~]# service neutron-l3-agent stop Stopping neutron-l3-agent: [ OK ] [root@puma05 ~]# ip netns | grep qrouter qrouter-69cf3535-2960-4b11-8e3a-da37c3331f01 [root@puma05 ~]# openstack-status == neutron services == neutron-server: inactive (disabled on boot) neutron-dhcp-agent: active neutron-l3-agent: inactive neutron-metadata-agent: active neutron-lbaas-agent: inactive (disabled on boot) neutron-openvswitch-agent: active == Support services == openvswitch: active messagebus: active
tested by service neutron-l3-agent restart I have run ping -ni 0.01 <floating ip> and no packet is lost openstack-neutron-2013.2.3-4.el6ost.noarch
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. http://rhn.redhat.com/errata/RHSA-2014-0516.html