yahoo-eng-team team mailing list archive

[Daniel Alvarez <1797084@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

When a network namespace is created, if the sysctl
fb_tunnels_only_for_init_net option is set to 0 (by default), fallback
tunnel devices will be automatically created if the initial namespace
had those in.

This leads to neutron ip_lib detecting namespaces as 'not empty' thus
unable to clean them up.

We need to add these devices so that they are taken into account when
determining if a namespace is empty or not.

More info at: https://www.kernel.org/doc/Documentation/sysctl/net.txt

** Affects: networking-ovn
     Importance: Undecided
         Status: New

** Affects: neutron
     Importance: Undecided
     Assignee: Daniel Alvarez (dalvarezs)
         Status: In Progress

** Also affects: networking-ovn
   Importance: Undecided
       Status: New

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

Title:
  Stale namespaces when fallback tunnels are present

Status in networking-ovn:
  New
Status in neutron:
  In Progress

Bug description:
  When a network namespace is created, if the sysctl
  fb_tunnels_only_for_init_net option is set to 0 (by default), fallback
  tunnel devices will be automatically created if the initial namespace
  had those in.

  This leads to neutron ip_lib detecting namespaces as 'not empty' thus
  unable to clean them up.

  We need to add these devices so that they are taken into account when
  determining if a namespace is empty or not.

  More info at: https://www.kernel.org/doc/Documentation/sysctl/net.txt

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