Public bug reported:
Meters and security groups use 'test_tenant' while all other resources
use 'test-tenant'.
This means that a test that creates multiple types of resources (While
using the the default tenant id) would find that some resources were
created under one tenant, and other resources under another tenant.
For example, a test creates a network, subnet, port, security group and
meter label + rule. Listing all resources that belong to the 'test-
tenant' would return a partial list, leading to confusing results.
** Affects: neutron
Importance: Undecided
Assignee: Assaf Muller (amuller)
Status: In Progress
** Tags: unittest
** Changed in: neutron
Assignee: (unassigned) => Assaf Muller (amuller)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1335821
Title:
Unit tests use inconsistent default tenant id
Status in OpenStack Neutron (virtual network service):
In Progress
Bug description:
Meters and security groups use 'test_tenant' while all other resources
use 'test-tenant'.
This means that a test that creates multiple types of resources (While
using the the default tenant id) would find that some resources were
created under one tenant, and other resources under another tenant.
For example, a test creates a network, subnet, port, security group
and meter label + rule. Listing all resources that belong to the
'test-tenant' would return a partial list, leading to confusing
results.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1335821/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
