touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #70549
[Bug 1444765] [NEW] admin's tenant_id is not the same with load_balancer's tenant_id in tempest tests
Public bug reported:
Here is the following scenario:
This is happening only WITH tempest tests by inheriting the necessary
class from 'tempest/api/neutron':
(a) When creating a loadbalancer for non_admin user, I could see the
'tenant_id' is equal to loadbalancer.get('tenant_id'). This sounds good
to me and requires no attention.
i.e.,
credentials = cls.isolated_creds.get_primary_creds()
mgr = tempest_clients.Manager(credentials=credentials)
auth_provider = mgr.get_auth_provider(credentials)
client_args = [auth_provider, 'network', 'regionOne']
(b) whereas, when I create a loadbalancer using admin credentials, the
tenant_id NOT equals loadbalancer.get('tenant_id'). In general it
SHOULD be equal.
i.e,.
credentials_admin = cls.isolated_creds.get_admin_creds()
mgr_admin = tempest_clients.Manager(credentials=credentials_admin)
auth_provider_admin = mgr_admin.get_auth_provider(credentials_admin)
client_args = [auth_provider_admin, 'network', 'regionOne']
Not sure why this is happening, the expected behavior should be "An
user(either admin/non-admin) should be able to create a loadbalancer for
the default tenant and that 'tenant_id' should be equal to the admin's
'tenant_id'. There are other test cases too specially for 'admin' role
got succeeded and behaving properly.
Details about the code can be found at
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/base.py
For the exact testcase:
(a) For admin_testcase: see line 55 - 61: https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_admin.py
(b) For non_admin testcase: see line 259 -266: https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_non_admin.py
** Affects: ifupdown (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1444765
Title:
admin's tenant_id is not the same with load_balancer's tenant_id in
tempest tests
Status in ifupdown package in Ubuntu:
New
Bug description:
Here is the following scenario:
This is happening only WITH tempest tests by inheriting the necessary
class from 'tempest/api/neutron':
(a) When creating a loadbalancer for non_admin user, I could see the
'tenant_id' is equal to loadbalancer.get('tenant_id'). This sounds
good to me and requires no attention.
i.e.,
credentials = cls.isolated_creds.get_primary_creds()
mgr = tempest_clients.Manager(credentials=credentials)
auth_provider = mgr.get_auth_provider(credentials)
client_args = [auth_provider, 'network', 'regionOne']
(b) whereas, when I create a loadbalancer using admin credentials,
the tenant_id NOT equals loadbalancer.get('tenant_id'). In general it
SHOULD be equal.
i.e,.
credentials_admin = cls.isolated_creds.get_admin_creds()
mgr_admin = tempest_clients.Manager(credentials=credentials_admin)
auth_provider_admin = mgr_admin.get_auth_provider(credentials_admin)
client_args = [auth_provider_admin, 'network', 'regionOne']
Not sure why this is happening, the expected behavior should be "An
user(either admin/non-admin) should be able to create a loadbalancer
for the default tenant and that 'tenant_id' should be equal to the
admin's 'tenant_id'. There are other test cases too specially for
'admin' role got succeeded and behaving properly.
Details about the code can be found at
https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/base.py
For the exact testcase:
(a) For admin_testcase: see line 55 - 61: https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_admin.py
(b) For non_admin testcase: see line 259 -266: https://review.openstack.org/#/c/171832/7/neutron_lbaas/tests/tempest/v2/api/test_load_balancers_non_admin.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1444765/+subscriptions
Follow ups
References