v3 support should not have an admin tenant in the default domain

Bug #1649874 reported by James Page on 2016-12-14
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack keystone charm
Medium
James Page
keystone (Juju Charms Collection)
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.

Tags: v3 Edit Tag help
James Page (james-page) on 2016-12-14
Changed in keystone (Juju Charms Collection):
milestone: none → 17.01
assignee: nobody → James Page (james-page)
importance: Undecided → Medium
status: New → In Progress
James Page (james-page) on 2016-12-14
tags: added: v3
James Page (james-page) on 2017-02-23
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

Change abandoned by James Page (<email address hidden>) on branch: master
Review: https://review.openstack.org/410725

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers