yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #21587
[Bug 1370868] [NEW] SDNVE plugin sets the tenant-name in the controller as the UUID instead of using the openstack project name
Public bug reported:
During neutron network-create operation, IBM SDN-VE plugin implicitly
also creates the tenant in the sdn-ve controller.
Its extract the tenant details using the keystone-client and issue a
POST for the tenant creation.
When this tenant gets created on the SDN-VE controller, the tenant-name
is being set to UUID of the openstack-tenant instead of the actual
project name.
The name of the tenant with the controller should be same as the
openstack project/tenant name
** Affects: neutron
Importance: Undecided
Assignee: Mamta Prabhu (mamtaprabhu)
Status: In Progress
** Tags: ibm
** Changed in: neutron
Assignee: (unassigned) => Mamta Prabhu (mamtaprabhu)
** Changed in: neutron
Status: New => In Progress
** Changed in: neutron
Assignee: Mamta Prabhu (mamtaprabhu) => (unassigned)
** Changed in: neutron
Assignee: (unassigned) => Mamta Prabhu (mamtaprabhu)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1370868
Title:
SDNVE plugin sets the tenant-name in the controller as the UUID
instead of using the openstack project name
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
During neutron network-create operation, IBM SDN-VE plugin implicitly
also creates the tenant in the sdn-ve controller.
Its extract the tenant details using the keystone-client and issue a
POST for the tenant creation.
When this tenant gets created on the SDN-VE controller, the tenant-
name is being set to UUID of the openstack-tenant instead of the
actual project name.
The name of the tenant with the controller should be same as the
openstack project/tenant name
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1370868/+subscriptions
Follow ups
References