OpenStack Heat

stack_domain_user_token is not implemented in KeystoneClientV2

Bug #1374230 reported by Steve Baker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Triaged
Low
Unassigned
OpenStack Heat no-milestone-taged-bugs

Bug Description

This prevents OS::Heat::WaitConditionHandle from being used with keystone v2, such as standalone mode (even though they would use SwiftSignal in standalone mode)

Steve Baker (steve-stevebaker)
no longer affects: tempest
Changed in heat:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Steven Hardy (shardy) wrote :

Steve, can you clarify the connection between v2 keystone and standalone mode - it that just because most public clouds still only offer v2 keystone?

TBH I was not really expecting the v2 contrib shim to maintain feature parity as we build out stuff depending on the stack domain users, but if folks want to contribute enhancements to it then I guess that's fine.

Revision history for this message
Steve Baker (steve-stevebaker) wrote :

I've made an initial assumption that standalone mode will always require v2 since v3 assumes there is a configured heat stack domain?

It would be nice if there was an enforced interface for these classes so that v2 stubs can be written whenever v3 methods are added.

Rico Lin (rico-lin)
Changed in heat:
milestone: none → no-priority-tag-bugs
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.