| 2015-07-10 10:33:24 |
Ievgeniia Zadorozhna |
bug |
|
|
added bug |
| 2015-07-10 10:33:43 |
Ievgeniia Zadorozhna |
tempest: assignee |
|
izadorozhna (izadorozhna) |
|
| 2015-07-10 10:34:22 |
Ievgeniia Zadorozhna |
summary |
Identity Client always uses adminURL enpoint, so cannot test public user actions |
Identity Client always uses adminURL enpoint, so cannot test public user actions correctly |
|
| 2015-07-10 10:34:39 |
Ievgeniia Zadorozhna |
summary |
Identity Client always uses adminURL enpoint, so cannot test public user actions correctly |
Identity Client always uses adminURL enpoint, so cannot test non-admin actions correctly |
|
| 2015-07-10 10:35:25 |
Ievgeniia Zadorozhna |
description |
The tempest Identity Client always is initialized with adminURL as the endpoint, it is hard-coded in tempest/tempest/clients.py in _set_identity_clients method.
This allows to run api/identity/admin tests with correct admin endpoint but this leads to the situation when we cannot run non-admin api/identity tests correctly, because non-admin user actions will try to use admin endpoint, when really publicURL endpoint is needed.
Now there is not many non-admin tests in api/identity and we are workinig oncreating new ones to expand the tempest coverage.
Since both admin and non-admin tests use the same identity_client we suggest that it's better to initialize identity_client with endpoint from tempest.conf ([identity]/enpoint_type) than the way to create two: public and admin identity clients.
The way where enpoint_type will be taken from config allows to run admin tests and non-admin tests in a separate way. |
The tempest Identity Client always is initialized with adminURL as the endpoint, it is hard-coded in tempest/tempest/clients.py in _set_identity_clients method.
This allows to run api/identity/admin tests with correct admin endpoint but this leads to the situation when we cannot run non-admin api/identity tests correctly, because non-admin user actions will try to use admin endpoint, when really publicURL endpoint is needed.
Now there is not many non-admin tests in api/identity and we are working on creating new ones to expand the tempest coverage.
Since both admin and non-admin tests use the same identity_client we suggest that it's better to initialize identity_client with endpoint from tempest.conf ([identity]/enpoint_type) than the way to create two: public and admin identity clients.
The way where enpoint_type will be taken from config allows to run admin tests and non-admin tests in a separate way. |
|
| 2015-07-10 10:36:13 |
Ievgeniia Zadorozhna |
description |
The tempest Identity Client always is initialized with adminURL as the endpoint, it is hard-coded in tempest/tempest/clients.py in _set_identity_clients method.
This allows to run api/identity/admin tests with correct admin endpoint but this leads to the situation when we cannot run non-admin api/identity tests correctly, because non-admin user actions will try to use admin endpoint, when really publicURL endpoint is needed.
Now there is not many non-admin tests in api/identity and we are working on creating new ones to expand the tempest coverage.
Since both admin and non-admin tests use the same identity_client we suggest that it's better to initialize identity_client with endpoint from tempest.conf ([identity]/enpoint_type) than the way to create two: public and admin identity clients.
The way where enpoint_type will be taken from config allows to run admin tests and non-admin tests in a separate way. |
The tempest Identity Client always is initialized with adminURL as the endpoint, it is hard-coded in tempest/tempest/clients.py in _set_identity_clients method.
This allows to run api/identity/admin tests with correct admin endpoint but this leads to the situation when we cannot run non-admin api/identity tests correctly, because non-admin user actions will try to use admin endpoint, when really publicURL endpoint is needed.
Now there is not many non-admin tests in api/identity and we are working on creating new ones to expand the tempest coverage.
Since both admin and non-admin tests use the same identity_client we suggest that it's better to initialize identity_client with endpoint from tempest.conf ([identity]/enpoint_type) than the way to create two: public and admin identity clients with the only one difference - enpoint_type.
The way where enpoint_type will be taken from config allows to run admin tests and non-admin tests in a separate way. |
|
| 2015-07-10 11:11:31 |
Sergey Slipushenko |
tempest: status |
New |
Confirmed |
|
| 2015-07-10 11:20:25 |
Sergey Slipushenko |
description |
The tempest Identity Client always is initialized with adminURL as the endpoint, it is hard-coded in tempest/tempest/clients.py in _set_identity_clients method.
This allows to run api/identity/admin tests with correct admin endpoint but this leads to the situation when we cannot run non-admin api/identity tests correctly, because non-admin user actions will try to use admin endpoint, when really publicURL endpoint is needed.
Now there is not many non-admin tests in api/identity and we are working on creating new ones to expand the tempest coverage.
Since both admin and non-admin tests use the same identity_client we suggest that it's better to initialize identity_client with endpoint from tempest.conf ([identity]/enpoint_type) than the way to create two: public and admin identity clients with the only one difference - enpoint_type.
The way where enpoint_type will be taken from config allows to run admin tests and non-admin tests in a separate way. |
The tempest Identity Client always is initialized with adminURL as the endpoint, it is hard-coded in tempest/tempest/clients.py in _set_identity_clients method.
This allows to run api/identity/admin tests with correct admin endpoint but this leads to the situation when we cannot run non-admin api/identity tests correctly, because non-admin user actions will try to use admin endpoint, when really publicURL endpoint is needed.
Now there is not many non-admin tests in api/identity and we (Refstack team) are working on creating new ones to expand the tempest coverage.
Since both admin and non-admin tests use the same identity_client we suggest that it's better to initialize identity_client with endpoint from tempest.conf ([identity]/enpoint_type) than the way to create two: public and admin identity clients with the only one difference - enpoint_type.
The way where enpoint_type will be taken from config allows to run admin tests and non-admin tests in a separate way. |
|
| 2015-07-10 11:45:44 |
OpenStack Infra |
tempest: status |
Confirmed |
In Progress |
|
| 2015-07-10 12:22:13 |
Andrea Frittoli |
tempest: importance |
Undecided |
Medium |
|
| 2015-07-11 14:31:36 |
OpenStack Infra |
tempest: assignee |
izadorozhna (izadorozhna) |
Sergey Slipushenko (sslypushenko) |
|
| 2015-07-13 07:00:23 |
Ievgeniia Zadorozhna |
tempest: assignee |
Sergey Slipushenko (sslypushenko) |
izadorozhna (izadorozhna) |
|
| 2015-07-15 20:18:18 |
Matthew Treinish |
bug |
|
|
added subscriber Matthew Treinish |
| 2015-07-18 20:38:55 |
OpenStack Infra |
tempest: assignee |
izadorozhna (izadorozhna) |
Sergey Slipushenko (sslypushenko) |
|
| 2015-08-03 14:04:15 |
Ievgeniia Zadorozhna |
tempest: assignee |
Sergey Slipushenko (sslypushenko) |
izadorozhna (izadorozhna) |
|
| 2015-08-04 19:22:16 |
OpenStack Infra |
tempest: assignee |
izadorozhna (izadorozhna) |
Brandon Palm (bapalm) |
|
| 2015-08-05 08:51:40 |
OpenStack Infra |
tempest: assignee |
Brandon Palm (bapalm) |
izadorozhna (izadorozhna) |
|
| 2015-08-05 17:31:17 |
OpenStack Infra |
tempest: status |
In Progress |
Fix Released |
|
