yahoo-eng-team team mailing list archive

[Armando Migliaccio <1705467@xxxxxxxxxxxxxxxxxx>]

As admin, you could create a network for a tenant that does not exist.
This is a 'well-known gotcha'. To address this we'd have to have neutron
talk to Keystone to validate that the UUID is a valid one. Doable, but
we never go around to do it for a variety of reasons (performance being
one of them).

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

** Changed in: neutron
   Importance: Undecided => Wishlist

** Summary changed:

- [Get me a network] auto-allocated networks does not verify tenant ID while creating
+ project ID is not verified when creating neutron resources

** Tags added: rfe

** Summary changed:

- project ID is not verified when creating neutron resources
+ [RFE] project ID is not verified when creating neutron resources

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

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

Title:
  [RFE] project ID is not verified when creating neutron resources

Status in neutron:
  Confirmed

Bug description:
  Environment: Ocata

  According to current docs, in order to create auto-allocated network
  in tenant, following command should be invoked:

  `neutron auto-allocated-topology-show [project_id]`

  Unfortunatelly, this command does not verify if given project exists,
  so it's easy to create completely unusefull network components, even
  breaking naming convention for project_id field in database tables.

  
  Example:

  » neutron auto-allocated-topology-show 37-e088febf-64bd-4b5e-b4dd-1f5a80e                                                                                                               
  +------------+--------------------------------------+
  | Field      | Value                                |
  +------------+--------------------------------------+
  | id         | 63f5f696-8a64-4bbb-af1e-b55a26f78f38 |
  | project_id | 37-e088febf-64bd-4b5e-b4dd-1f5a80e   |
  | tenant_id  | 37-e088febf-64bd-4b5e-b4dd-1f5a80e   |
  +------------+--------------------------------------+

  »

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