v3 catalog not implemented for templated backend
Bug #1313458 reported by
Brant Knudson
This bug affects 5 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Wishlist
|
Brant Knudson | ||
Icehouse |
Fix Released
|
Wishlist
|
Kieran Spear |
Bug Description
The templated backend didn't implement the method to get a v3 catalog. So you couldn't get a valid v3 token when the templated catalog backend was configured.
Changed in keystone: | |
assignee: | nobody → Brant Knudson (blk-u) |
importance: | Undecided → Wishlist |
Changed in keystone: | |
status: | New → In Progress |
Changed in keystone: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | juno-1 → 2014.2 |
tags: | removed: in-stable-icehouse |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/70630 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=8b9580456aa 4223184f612330c 31077624dbf0ff
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8b9580456aa4223 184f612330c3107 7624dbf0ff
Author: Brant Knudson <email address hidden>
Date: Sun Feb 2 15:17:13 2014 -0600
Catalog driver generates v3 catalog from v2 catalog
The default get_v3_catalog method in the catalog driver would just
raise NotImplemented. This method is given a default implementation
that generates the v3 catalog by translating the v2 catalog.
With this change, the templated and kvs catalog backends can
generate a v3 catalog.
Closes-Bug: #1313458 e0e9e370f48f7ee 3643bd2fe3d
Change-Id: I1646c7dcab90f2