BUG reported: https://bugs.launchpad.net/neutron/+bug/1689880
On 10 May 2017 at 10:49, Martinx - ジェームズ wrote:
> Hello,
>
> I'm playing with Networking OVN, and planning to deploy it into
> production in a couple weeks.
>
> After deploying everything and starting using OVN, with Floating IPs,
> multiple compute nodes and everything else, I can say that it looks
> awesome! Way better than "neutron-*-agents".
>
> However, I noted that after running:
>
> ---
> systemctl restart neutron-server
> ---
>
> Literally ALL my stacks, on all projects, becomes unreachable!!!
>
> After double checking everything, I did one single change in my
> ml2_conf.ini, from:
>
> ---
> neutron_sync_mode = repair
> ---
>
> To:
>
> ---
> # neutron_sync_mode = off
> ---
>
> Then, problem solved!
>
> Now, I can restart the neutron-server without any problems!
>
> Deep inside me, I'm freaking out with this... Because this whole OVN
> solution looks very, very delicate. I mean, what to do if this happens
> again?
>
> Ask ALL my customers to rebuild their stacks?!
>
> How to REALLY repair OVN?
>
> Now that the problem is solved, I'll keep trying to use and stress test
> it even more but, I'm losing confidence on Networking OVN on its current
> state.
>
> I'm using Ubuntu 16.04 with Kernel 4.8 (HWE), plus Ocata from Cloud
> Archive.
>
> Cheers!
> Thiago
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
