← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1649092] [NEW] Cleaning snat namespace didn't unplug external device

 

Public bug reported:

[1] allow us to identify the stale snat namespace and delete the
namespace when the gateway is cleared as the agent restarts.

But method SnatNamespace.delete unplugs 'sg-XXX' devices only, leads to
stale port remains in ovs bridge.

[1] https://review.openstack.org/#/c/326729/


How to reproduce:

- create a distributed router, set its router gateway, bind a subnet to it
- stop the l3 agent hosting the router
- clear the router’s gateway
- start the stopped l3 agent, device "sg-XXXX" and snat namespace will be cleaned, stale device “qg-XXXX” will remain.

$ sudo ovs-vsctl list port qg-749cbaab-13
_uuid               : 7f116611-4885-4813-a938-a9aebf2723ac
bond_downdelay      : 0
bond_fake_iface     : false
bond_mode           : []
bond_updelay        : 0
external_ids        : {}
fake_bridge         : false
interfaces          : [81e93ffd-ce76-4c75-8522-5ff5e9a4c1c0]
lacp                : []
mac                 : []
name                : "qg-749cbaab-13"
other_config        : {net_uuid="eaad0784-47dd-4263-82e1-419e7f3d8e3f", network_type=vxlan, physical_network=None, segmentation_id="101", tag="7"}
qos                 : []
statistics          : {}
status              : {}
tag                 : 4095
trunks              : []
vlan_mode           : []

** Affects: neutron
     Importance: Undecided
     Assignee: Quan Tian (tianquan23)
         Status: In Progress

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

Title:
  Cleaning snat namespace didn't unplug external device

Status in neutron:
  In Progress

Bug description:
  [1] allow us to identify the stale snat namespace and delete the
  namespace when the gateway is cleared as the agent restarts.

  But method SnatNamespace.delete unplugs 'sg-XXX' devices only, leads
  to stale port remains in ovs bridge.

  [1] https://review.openstack.org/#/c/326729/

  
  How to reproduce:

  - create a distributed router, set its router gateway, bind a subnet to it
  - stop the l3 agent hosting the router
  - clear the router’s gateway
  - start the stopped l3 agent, device "sg-XXXX" and snat namespace will be cleaned, stale device “qg-XXXX” will remain.

  $ sudo ovs-vsctl list port qg-749cbaab-13
  _uuid               : 7f116611-4885-4813-a938-a9aebf2723ac
  bond_downdelay      : 0
  bond_fake_iface     : false
  bond_mode           : []
  bond_updelay        : 0
  external_ids        : {}
  fake_bridge         : false
  interfaces          : [81e93ffd-ce76-4c75-8522-5ff5e9a4c1c0]
  lacp                : []
  mac                 : []
  name                : "qg-749cbaab-13"
  other_config        : {net_uuid="eaad0784-47dd-4263-82e1-419e7f3d8e3f", network_type=vxlan, physical_network=None, segmentation_id="101", tag="7"}
  qos                 : []
  statistics          : {}
  status              : {}
  tag                 : 4095
  trunks              : []
  vlan_mode           : []

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


Follow ups