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 fi
: Wednesday, August 05, 2015 12:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [neutron][dvr] Removing fip namespace when restarting
L3 agent.
Hi all,
During testing of Neutron upgrades, I have found that restarting the L3 agent
in DVR mode is causing
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.korzeniew...@intel.com> wrote:
> Hi all,
>
> During testing of Neutron upgrades, I have f
ternal/pids/8223e12e-837b-49d4-9793-63603fccbc9f.pid
And after finishing the sync loop, the fip namespace is deleted…
Regards,
Artur
From: Kevin Benton [mailto:blak...@gmail.com]
Sent: Thursday, August 6, 2015 7:40 AM
To: OpenStack Development Mailing List (not for usage questions)
rface inside the fip namespace is not deleted, the VM has full
> internet access without any downtime.
>
>
>
> Ca we consider it a bug? I guess it is something in startup/full-sync
> logic since the log is saying:
>
>
> /opt/openstack/data/neutron/external/pids/8223e12e-8
finishing the sync loop, the fip namespace is deleted…
Regards,
Artur
From: Kevin Benton [mailto:blak...@gmail.com<mailto:blak...@gmail.com>]
Sent: Thursday, August 6, 2015 7:40 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [neutron][dvr] Re
tur
>
>
>
> *From:* Oleg Bondarev [mailto:obonda...@mirantis.com]
> *Sent:* Thursday, August 6, 2015 5:18 PM
>
> *To:* OpenStack Development Mailing List (not for usage questions)
> *Subject:* Re: [openstack-dev] [neutron][dvr] Removing fip namespace when
> restarting L3 agent.
