Bug 1425533
Summary: | [RFE] Option to configure Keystone v3 on OSP deployment via the Director | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Irina Petrova <ipetrova> |
Component: | instack-undercloud | Assignee: | James Slagle <jslagle> |
Status: | CLOSED ERRATA | QA Contact: | Arik Chernetsky <achernet> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 12.0 (Pike) | CC: | cpaquin, dbecker, emacchi, gcharot, jcoufal, josorior, jpullen, kbasil, mburns, mcornea, morazi, nkinder, nlevinki, pablo.iranzo, panbalag, rajini.karthik, raywang, rcritten, rduartes, rhel-osp-director-maint, tvignaud |
Target Milestone: | Upstream M2 | Keywords: | FutureFeature, Triaged |
Target Release: | 12.0 (Pike) | ||
Hardware: | noarch | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | instack-undercloud-7.0.0-0.20170503001109.el7ost | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-13 21:08:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 1335596, 1356451, 1426284, 1434928, 1434929, 1434931, 1442136, 1469330 |
Description
Irina Petrova
2017-02-21 16:43:26 UTC
Work can be tracked here: https://blueprints.launchpad.net/tripleo/+spec/keystone-v3 This looks mostly complete upstream: https://review.openstack.org/#/q/topic:bp/keystone-v3,n,z The only outstanding review appears to be for having stackrc use v3 in instack-undercloud. Is there anything else outstanding that is still using the v2 Identity API? Well, the undercloud commit is not really just the stackrc but a bunch of services whose API we use v2 for. Hopefully that patch is merging soon as we got finally a release for mistralclient which is what we needed to make that work. *** Bug 1434928 has been marked as a duplicate of this bug. *** *** Bug 1434923 has been marked as a duplicate of this bug. *** Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:3462 |