yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1884254@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In case when neutron-ovs-agent is restarted and there is rabbitmq connectivity issue, traffic through provider networks may be broken. It is similar issue like described in https://launchpad.net/neutron/+bug/1803919 and then it was fixed by setting up rpc and checking if connectivity is fine before physical bridges were configured.
But later bug https://launchpad.net/neutron/+bug/1840443 came and fix for that https://github.com/openstack/neutron/commit/d41bd58f31e259fe408c8c059b31299fdfe81127 changed this order again. So now physical bridges are configured before rpc is configured so it may happen again that due to broken rpc channel correct flows will not be installed.

** Affects: neutron
     Importance: Low
         Status: New


** Tags: ovs

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

Title:
  Restart of neutron-ovs-agent may cause data plane breakege

Status in neutron:
  New

Bug description:
  In case when neutron-ovs-agent is restarted and there is rabbitmq connectivity issue, traffic through provider networks may be broken. It is similar issue like described in https://launchpad.net/neutron/+bug/1803919 and then it was fixed by setting up rpc and checking if connectivity is fine before physical bridges were configured.
  But later bug https://launchpad.net/neutron/+bug/1840443 came and fix for that https://github.com/openstack/neutron/commit/d41bd58f31e259fe408c8c059b31299fdfe81127 changed this order again. So now physical bridges are configured before rpc is configured so it may happen again that due to broken rpc channel correct flows will not be installed.

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