yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1835808@xxxxxxxxxxxxxxxxxx>]

Thx Swami for pointing to this patch. I have no idea how I missed that
this is fixed there. So in fact it is issue only in our older D/S
branch. We can close this bug then :)

** Changed in: neutron
       Status: Confirmed => Invalid

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

Title:
  DVR router with configured external_network_bridge option don't have
  external connectivity

Status in neutron:
  Invalid

Bug description:
  Config option "external_network_bridge" was removed in Stein release
  but in versions Rocky and Queens where it still exists, if it is
  configured for dvr router it will cause problem with FIP connectivity.

  It is like that because some time ago, commit
  https://github.com/openstack/neutron/commit/88f5e11d8bf820b0124be0f6ec3c2d96011592d9
  introduced functionality which avoids connecting trunk ports to the
  ovs bridge. It is fine in most cases as neutron-ovs-agent is then
  managing such ports and it works fine but in case when
  external_network_bridge config option is set, fip gateway port (fg-
  xxx) is plugged directly into this external bridge and than it isn't
  managed by neutron-ovs-agent. So dead vlan tag isn't never removed and
  connectivity don't work.

  It looks like we are missing code like
  https://github.com/openstack/neutron/blob/stable/queens/neutron/agent/l3/router_info.py#L658
  in
  https://github.com/openstack/neutron/blob/master/neutron/agent/l3/dvr_fip_ns.py#L153

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