MOS 7.0-8.0-9.0 and updates are not compatible with keystone v3

Bug #1593712 reported by Robert Duncan on 2016-06-17
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
MOS Keystone

Bug Description

I have logged some bugs regarding keystone v3 support for ceph radosgw, murano and the release notes.

they are mostly medium or whishlist priority - one is marked as invalid

Murano and domain users

Murano and federated users

Docs bug

So I'm logging this as a general can't use identity API v3 with MOS, I think it's a valid bug because we still can't federate users or use Fuel to deploy keystone 3

Dmitry Klenov (dklenov) wrote :

Keystone team, please validate that this request is valid. To me it is better to properly work with mentioned in the description.

Changed in fuel:
milestone: none → 10.0
assignee: nobody → MOS Keystone (mos-keystone)
importance: Undecided → Medium
status: New → Confirmed
tags: added: area-mos

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result


expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see

tags: added: need-info
Boris Bobrov (bbobrov) wrote :

Thank you, it's good to have a list of v3-related issues. I am moving this to "wishlist" because it is used to track other issues, it should be closed when all of them are closed.

Changed in fuel:
importance: Medium → Wishlist
milestone: 10.0 → none
Changed in fuel:
milestone: none → 9.1
Roman Vyalov (r0mikiam) on 2016-10-13
Changed in fuel:
milestone: 9.1 → 9.2
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers