Keystone v2 wrapper does not respect region

Bug #1422763 reported by Drago
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
High
Drago

Bug Description

When using the OS::Heat::Stack resource and the Keystone v2 wrapper, the stacks created by OS::Heat::Stack are spun up in the same region as the Heat instance consuming the parent template, regardless of the region_name specified in the template.

Tags: multi-region
Changed in heat:
assignee: nobody → Drago (drago-rosson)
status: New → In Progress
Angus Salkeld (asalkeld)
Changed in heat:
importance: Undecided → High
milestone: none → liberty-1
status: In Progress → Triaged
Revision history for this message
Drago (dragorosson) wrote :

The fix for this bug was https://review.openstack.org/#/c/155798/ which was merged. It was my first contribution, so I missed the #closes-bug line in the commit message. What should be done about this?

Changed in heat:
status: Triaged → Fix Committed
milestone: liberty-1 → kilo-rc1
Thierry Carrez (ttx)
Changed in heat:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in heat:
milestone: kilo-rc1 → 2015.1.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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