AccessKey/WaitConditionHandle ec2 keypair incorrect
Bug #1089035 reported by
Steven Hardy
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steven Hardy | ||
Grizzly |
Fix Released
|
High
|
Steven Hardy |
Bug Description
It seems that despite passing the user_id of the in-instance keystone user to the underlying self.client.ec2* calls to keystoneclient, we end up passing the ec2 credentials owned by the user creating the stack via AccessKey and WaitConditionHa
I don't see what we are doing wrong, so this may be a keystone or keystoneclient bug - I'm investigating.
Changed in heat: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Steven Hardy (shardy) |
milestone: | none → grizzly-2 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
Investigated, not a keystone bug, there is a bug in heat/common/ heat_keystonecl ient.py meaning the context user_id is used instead of the AccessKey/ WaitConditionHa ndle related user. I have a fix, currently testing.