yahoo-eng-team team mailing list archive

[Kevin Benton <1689880@xxxxxxxxxxxxxxxxxx>]

** Project changed: neutron => networking-ovn

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1689880

Title:
  The "neutron_sync_mode = repair" option breaks the whole cloud!

Status in networking-ovn:
  New

Bug description:
  Hello,

   I'm using Ubuntu 16.04 with Kernel 4.8 (HWE), plus Ocata from Cloud
  Archive. 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,
  Security Groups, multiple compute nodes and everything else, I can say
  that it looks awesome! Way better than the "neutron-*-agents".

   However, I noted that after running:

  ---
   systemctl restart neutron-server
  ---

   Literally ALL my stacks, on all projects, becomes unreachable!!!

   The Instances could not even ping its own Floating IP anymore, and of
  course, the Internet.

   Also, the Internet could not reach the Instances via its Floating
  IPs...

   After double checking the config files, and comparing it with the
  doc*, 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!

   What to do if this happens again?

   Ask ALL my customers to rebuild their stacks?!

   How to REALLY repair OVN if something like this happen again?

   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.

  
  * doc: https://docs.openstack.org/developer/networking-ovn/install.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/networking-ovn/+bug/1689880/+subscriptions