v3 support should not have an admin tenant in the default domain
Bug #1649874 reported by
James Page
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Keystone Charm |
Triaged
|
Medium
|
Unassigned | ||
| keystone (Juju Charms Collection) |
Invalid
|
Medium
|
James Page | ||
Bug Description
Currently, for both v2 and v3 deployments, an admin tenant/project is created under the default domain; this is really surplus to requirements in a v3 deployment as the admin user should be using the admin tenant under the admin_domain.
Lets drop this for the next release.
| Changed in keystone (Juju Charms Collection): | |
| milestone: | none → 17.01 |
| assignee: | nobody → James Page (james-page) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to charm-keystone (master) | #1 |
| tags: | added: v3 |
| Changed in charm-keystone: | |
| assignee: | nobody → James Page (james-page) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| Changed in keystone (Juju Charms Collection): | |
| status: | In Progress → Invalid |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Change abandoned on charm-keystone (master) | #2 |
| Changed in charm-keystone: | |
| assignee: | James Page (james-page) → nobody |
| status: | In Progress → Triaged |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/