| 2016-04-04 02:11:11 |
Michael Richardson |
bug |
|
|
added bug |
| 2016-04-04 02:11:49 |
Michael Richardson |
description |
Many default tests appear to request credentials without specifying a role. These tests then fail in an environment where more granular roles have been implemented (for example, with the addition of roles to both keystone and policy.json files that have fewer permissions than _member_) and as a result, the historical notion of "any role on a project is generally equivalent to admin_or_owner" no longer applies.
If credentials are added to accounts.yaml with roles less permissive than _member_, there is a chance that the default tests will use them and fail. For example,
tempest.api.compute.keypairs.test_keypairs.KeyPairsV2TestJSON.test_keypair_create_delete
- will fail if there is are credentials in account in accounts.yaml, whose only defined purpose via the various policy.json files is to start and stop compute instances.
A preferable outcome would be either for a default role to be applied (e.g. _member_) if none were requested from the credential provider by the test itself, or for the individual tests themselves to always request credentials by role. |
Many default tests appear to request credentials without specifying a role. These tests then fail in an environment where more granular roles have been implemented (for example, with the addition of roles to both keystone and policy.json files that have fewer permissions than _member_) and as a result, the historical notion of "any role on a project is generally equivalent to admin_or_owner" no longer applies.
If credentials are added to accounts.yaml with roles less permissive than _member_, there is a chance that the default tests will use them and fail. For example,
tempest.api.compute.keypairs.test_keypairs.KeyPairsV2TestJSON.test_keypair_create_delete
- will fail if there are credentials in account in accounts.yaml, whose only defined purpose via the various policy.json files is to start and stop compute instances.
A preferable outcome would be either for a default role to be applied (e.g. _member_) if none were requested from the credential provider by the test itself, or for the individual tests themselves to always request credentials by role. |
|
| 2016-04-04 02:15:19 |
Michael Richardson |
description |
Many default tests appear to request credentials without specifying a role. These tests then fail in an environment where more granular roles have been implemented (for example, with the addition of roles to both keystone and policy.json files that have fewer permissions than _member_) and as a result, the historical notion of "any role on a project is generally equivalent to admin_or_owner" no longer applies.
If credentials are added to accounts.yaml with roles less permissive than _member_, there is a chance that the default tests will use them and fail. For example,
tempest.api.compute.keypairs.test_keypairs.KeyPairsV2TestJSON.test_keypair_create_delete
- will fail if there are credentials in account in accounts.yaml, whose only defined purpose via the various policy.json files is to start and stop compute instances.
A preferable outcome would be either for a default role to be applied (e.g. _member_) if none were requested from the credential provider by the test itself, or for the individual tests themselves to always request credentials by role. |
Many default tests appear to request credentials without specifying a role. These tests then fail in an environment where more granular roles have been implemented (for example, with the addition of roles to both keystone and policy.json files that have fewer permissions than _member_) and as a result, the historical notion of "any role on a project is generally equivalent to admin_or_owner" no longer applies.
If credentials are added to accounts.yaml with roles less permissive than _member_, there is a chance that the default tests will use them and fail. For example,
tempest.api.compute.keypairs.test_keypairs.KeyPairsV2TestJSON.test_keypair_create_delete
- will fail if there are credentials in accounts.yaml, whose only defined purpose via the various policy.json files is to start and stop compute instances.
A preferable outcome would be either for a default role to be applied (e.g. _member_) if none were requested from the credential provider by the test itself, or for the individual tests themselves to always request credentials by role. |
|
| 2016-04-04 02:19:54 |
Michael Richardson |
description |
Many default tests appear to request credentials without specifying a role. These tests then fail in an environment where more granular roles have been implemented (for example, with the addition of roles to both keystone and policy.json files that have fewer permissions than _member_) and as a result, the historical notion of "any role on a project is generally equivalent to admin_or_owner" no longer applies.
If credentials are added to accounts.yaml with roles less permissive than _member_, there is a chance that the default tests will use them and fail. For example,
tempest.api.compute.keypairs.test_keypairs.KeyPairsV2TestJSON.test_keypair_create_delete
- will fail if there are credentials in accounts.yaml, whose only defined purpose via the various policy.json files is to start and stop compute instances.
A preferable outcome would be either for a default role to be applied (e.g. _member_) if none were requested from the credential provider by the test itself, or for the individual tests themselves to always request credentials by role. |
Many default tests appear to request credentials without specifying a role. These tests then fail in an environment where more granular roles have been implemented (for example, with the addition of roles to both keystone and policy.json files that have fewer permissions than _member_) and as a result, the historical notion of "any role on a project is generally equivalent to admin_or_owner" no longer applies.
If credentials are added to accounts.yaml with roles less permissive than _member_, there is a chance that the default tests will use them and fail.
For example,
tempest.api.compute.keypairs.test_keypairs.KeyPairsV2TestJSON.test_keypair_create_delete
- will fail if there are credentials in accounts.yaml, whose only defined purpose via the various policy.json files is to start and stop compute instances.
A preferable outcome would be either for a default role to be applied (e.g. _member_) if none were requested from the credential provider by the test itself, or for the individual tests themselves to always request credentials by role. |
|
| 2016-04-05 15:06:01 |
Dale Smith |
bug |
|
|
added subscriber Dale Smith |
| 2016-04-06 15:51:38 |
OpenStack Infra |
tempest: status |
New |
In Progress |
|
| 2016-04-06 15:51:38 |
OpenStack Infra |
tempest: assignee |
|
Dale Smith (dalees) |
|
| 2020-03-20 19:52:09 |
Martin Kopec |
tempest: status |
In Progress |
Incomplete |
|
| 2020-03-20 19:52:09 |
Martin Kopec |
tempest: assignee |
Dale Smith (dalees) |
|
|
| 2020-05-20 04:17:30 |
Launchpad Janitor |
tempest: status |
Incomplete |
Expired |
|
