yahoo-eng-team team mailing list archive

[Slawek Kaplonski <1798085@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In fullstack tests L3 agent is not running in host namespace currently. That works fine e.g. with Linuxbridge agent, which is spawned in host-XXX namespace when test is creating and connecting FakeVM as it is always done in this host namespace and agent can see it.
However in case of using L3 agent this won't work because L3 agent creates veth connection between qrouter- namespace and global scope (no namespace) so linuxbridge agent can't see such tap device and is not creating proper network configuration for such router interfaces.

** Affects: neutron
     Importance: Medium
     Assignee: Slawek Kaplonski (slaweq)
         Status: Confirmed


** Tags: fullstack

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

Title:
  [Fullstack] L3 agent should be run in host namespace, together with L2
  agent

Status in neutron:
  Confirmed

Bug description:
  In fullstack tests L3 agent is not running in host namespace currently. That works fine e.g. with Linuxbridge agent, which is spawned in host-XXX namespace when test is creating and connecting FakeVM as it is always done in this host namespace and agent can see it.
  However in case of using L3 agent this won't work because L3 agent creates veth connection between qrouter- namespace and global scope (no namespace) so linuxbridge agent can't see such tap device and is not creating proper network configuration for such router interfaces.

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