yahoo-eng-team team mailing list archive

[Gaurav Kaushik <gkaushik@xxxxxxxxxx>]

Public bug reported:

Steps to Reproduce:-

1) Create a few tenants(may be 4 to 5)
2) Create Networks,subnets, routers and connect them
3) Create vpnaas(site-to-site connection) in between two tenants
4) Boot up vms and docker containers behind the vpnaas
5) Send PING traffic between the docker containers across tenants
6) After the test, delete all the namespaces, networks tenants etc
7) Check in the Openstack dashboard and cli, the networks related tio different tenants are
still listed as "Active" with the tenant names which are ALREADY DELETED.

This issue is found in Juno release:
root@controller:~# nova-manage version
2014.2.3
root@controller:~#

** Affects: neutron
     Importance: Undecided
         Status: New

** Attachment added: "Jnuk entries.png"
   https://bugs.launchpad.net/bugs/1498704/+attachment/4471738/+files/Jnuk%20entries.png

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

Title:
  Tenant junk entries found in the controller Even after deletion

Status in neutron:
  New

Bug description:
  Steps to Reproduce:-

  1) Create a few tenants(may be 4 to 5)
  2) Create Networks,subnets, routers and connect them
  3) Create vpnaas(site-to-site connection) in between two tenants
  4) Boot up vms and docker containers behind the vpnaas
  5) Send PING traffic between the docker containers across tenants
  6) After the test, delete all the namespaces, networks tenants etc
  7) Check in the Openstack dashboard and cli, the networks related tio different tenants are
  still listed as "Active" with the tenant names which are ALREADY DELETED.

  This issue is found in Juno release:
  root@controller:~# nova-manage version
  2014.2.3
  root@controller:~#

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