yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1866635@xxxxxxxxxxxxxxxxxx>]

[Expired for neutron because there has been no activity for 60 days.]

** Changed in: neutron
       Status: Incomplete => Expired

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

Title:
  router-update for internal networking not correct when restarting ovs-
  agent

Status in neutron:
  Expired

Bug description:
  In our production environment, running Rocky (Neutron 13.0.5 + this
  patch: https://review.opendev.org/#/c/693681/), we've experienced some
  missing network route for our internal networking.

  We have:

  one VM-1 on 192.168.2.20, on compute-1

  one VM-2 on 192.168.2.3, compute-2

  Our VM-1 also has a floating IP, and is used to monitor VM-2 (VM-1
  contains a Zabbix proxy).

  Let's say ones reboot compute-1, Neutron misses the necessary rules to
  connect VM-1 to VM-2. Restarting VM-2 adds new OVS flow rules on
  compute-1, which restores connectivity. Restarting ovs-agent on
  compute-1 has no effect, which means that there's a problem there.

  Please help us fixing the bug.

  Cheers,

  Thomas Goirand (zigo)

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1866635/+subscriptions