yahoo-eng-team team mailing list archive

[Hong Hui Xiao <xiaohhui@xxxxxxxxxx>]

Public bug reported:

Steps to reproduce:
1) Create a network with tenant id A.

2)
    2.1) Create a port/subnet in that network, and specify tenant B as the --tenant-id.
    OR
    2.2) User authenticates with tenant B. Then user creates a port/subnet in that network, without specifying tenant id.

Problem:
Now we have a network with port/subnet in it. But they are not in one tenant. 

I checked the neutron code, and found that there is no restriction of tenant for creating port/subnet. 
If a network has port/subnet in it, it is meaningful to have them all in one tenant.

** Affects: neutron
     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/1389246

Title:
  port/subnet tenant id and network tenant id could be inconsistent

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  Steps to reproduce:
  1) Create a network with tenant id A.

  2)
      2.1) Create a port/subnet in that network, and specify tenant B as the --tenant-id.
      OR
      2.2) User authenticates with tenant B. Then user creates a port/subnet in that network, without specifying tenant id.

  Problem:
  Now we have a network with port/subnet in it. But they are not in one tenant. 

  I checked the neutron code, and found that there is no restriction of tenant for creating port/subnet. 
  If a network has port/subnet in it, it is meaningful to have them all in one tenant.

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