Can you try setting the following to False: https://github.com/openstack/neutron/blob/dc0944f2d4e347922054bba679ba7f5d1ae6ffe2/etc/l3_agent.ini#L97 On Wed, Aug 5, 2015 at 3:36 PM, Korzeniewski, Artur < artur.korzeniewski at intel.com> wrote: > Hi all, > > During testing of Neutron upgrades, I have found that restarting the L3 > agent in DVR mode is causing the VM network downtime for configured > floating IP. > > The lockdown is visible when pinging the VM from external network, 2-3 > pings are lost. > > The responsible place in code is: > > DVR: destroy fip ns: fip-8223e12e-837b-49d4-9793-63603fccbc9f from > (pid=156888) delete > /opt/openstack/neutron/neutron/agent/l3/dvr_fip_ns.py:164 > > > > Can someone explain why the fip namespace is deleted? Can we workout the > situation, when there is no downtime of VM access? > > > > Artur Korzeniewski > > -------------------------------------------- > > Intel Technology Poland sp. z o.o. > > KRS 101882 > > ul. Slowackiego 173, 80-298 Gdansk > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > -- Kevin Benton -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150806/42bc62e9/attachment.html>