yahoo-eng-team team mailing list archive

[Ann Kamyshnikova <akamyshnikova@xxxxxxxxxxxx>]

Seems that wrong command was used to show all networks that belongs to
current tenant. I run

neutron net-list -- --tenant_id TENANT_ID

And it shows correctly only list of networks which belongs to that
tenant.  Flag --os-tenant-id means the authentication tenant ID, it is
not the same as list with filtering on tenant_id. Here is example of
running commands with --debug flag
http://paste.openstack.org/show/142516/. It shows that "neutron --os-
tenant-id TENANT_ID net-list" sends request without specification of
tenant_id and "neutron net-list -- --tenant_id TENANT_ID" specifies it.

** Changed in: neutron
       Status: Confirmed => Opinion

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

Title:
  Neutron net-list returns all networks for user in multiple tenants

Status in OpenStack Neutron (virtual network service):
  Opinion

Bug description:
  I have a user, who belongs to multiple tenants.

  When executing neutron net-list (specifying the tenant id), neutron
  returns all networks for all of the tenants my user belongs to; I
  would expect it to only return the networks for the specified tenant.

  e.g.

  neutron --os-tenant-id 0dc52bffe50d47f7a42674969bd29f3c net-list
  +--------------------------------------+------------+-----------------------------------------------------+
  | id                                   | name       | subnets                                             |
  +--------------------------------------+------------+-----------------------------------------------------+
  | 11e304ec-5b67-4980-aa57-da10d0f057a6 | Content    | 3d550793-2da9-4354-9243-0a071a5aa5d8 172.16.0.0/24  |
  | 3942eef0-8fe8-4ec1-aa3b-77a4c40ab1fc | Internal   | 479785e7-246d-473a-8cb1-4730240342b3 192.168.0.0/24 |
  | 3aed9b6b-387b-4b9d-a9e4-a4bdeab349b7 | Internal   | d6ab13ff-2de4-44f9-ac07-b4bb998d2b72 192.168.0.0/24 |
  | 3d4883f9-7b3d-4ef1-a293-419127bc958c | Content    | 22c7d766-ea8b-4e42-9830-82fe8b239b3f 172.16.0.0/24  |
  | 5bab1a18-34fa-400e-a357-cb4d16e4b0b2 | Content    | aaa60d54-dd84-4a39-9fee-dc928ef1b532 172.16.0.0/24  |
  | 6edaf1b2-bbd1-4ae4-b3a4-faea5ebf3732 | Internal   | be944439-ecea-4006-9fca-c4402c461360 192.168.0.0/24 |
  | 71533970-1cb6-415c-9845-0e850f08526b | Internal   | c6efc50b-17ba-4dc4-9602-12e4a5dff9a7 192.168.0.0/24 |
  | 937d50a0-c07a-49e5-8d5e-277a21a79a60 | ext_net    |                                                     |
  | 9b3cb15d-099d-4673-97b6-fbcd9181962f | Management | 0ddb260e-1f30-4def-8304-19733a90c860 10.20.76.0/24  |
  | 9c534554-7d5d-47d8-8305-28af162c9c52 | Content    | a73f7e75-d1eb-4f96-b25a-ba2d832c7c76 172.16.0.0/24  |
  | a2031601-6a01-4986-b984-98eb0701f393 | Management | 803a6c01-a78b-47a8-bc51-e4e698283128 10.20.78.0/24  |
  | ac9af807-8205-4649-80c4-962202a6ac8c | Management | 08650fa9-7fe4-481a-a0ab-357455e658ad 10.20.77.0/24  |
  +--------------------------------------+------------+-----------------------------------------------------+

  The problem is in a multi-tenant environment, I deploy multiple
  networks with the same names.  This means I cannot look up networks by
  name, but must always use the unique ID.  This makes
  templating/scripting more challenging.

  If I were to execute  'nova --os-tenant-id
  0dc52bffe50d47f7a42674969bd29f3c list' as the same user, this will
  only list the instances in the specified tenant.

  Neutron should behave in the same way.

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