35fc95dbd0
We have a bug in dynamic creds creation where project creds with different roles are created under a new projects. Creds of different role of projects must be created within the same project. Fixing the creation of 'project_admin', 'project_member', 'project_reader', 'primary' creds in same projects. All the alt creds will be created under same projects. but main and alt creds will use different project, for example, 'project_alt_member' and 'project_member' creds will be created in different project. 'admin' creds will continue be in new project as many test use it as legacy admin. Closes-Bug: #1964509 Change-Id: I9af005e2900195c42ecbbf7434facae2d3952f30
20 lines
1.0 KiB
YAML
20 lines
1.0 KiB
YAML
---
|
|
fixes:
|
|
- |
|
|
There was a bug (bug#1964509) in dynamic credentials creation where
|
|
project credentials with different roles are created with the new
|
|
projects. Credential of different role of projects must be created
|
|
within the same project. For exmaple, 'project_admin', 'project_member',
|
|
'project_reader', and 'primary', credentials will be created in the
|
|
same projects. 'alt', 'project_alt_admin', 'project_alt_member',
|
|
'project_alt_reader' will be created within the same project.
|
|
|
|
'admin' credenatials is considered and kept as legacy admin and
|
|
will be created under new project. If any test want to test with
|
|
admin role in projectA and non-admin/admin in projectB then test
|
|
can request projectA admin using 'admin' or 'project_alt_admin'
|
|
and non-admin in projectB using 'primary', 'project_member',
|
|
or 'project_reader'/admin in projectB using 'project_admin'. Many
|
|
existing tests using the 'admin' with new project to assert on the
|
|
resource list so we are keeping 'admin' a kind of legacy admin.
|