ec2tokens authentication is failing during Heat tests
Bug #1484086 reported by
Thomas Herve
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Thomas Herve | ||
Kilo |
Fix Released
|
High
|
Unassigned | ||
OpenStack Identity (keystone) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
As seen here for example: http://
We're getting the error: "Non-default domain is not supported" which seems to have been introduced here: https:/
Changed in heat: | |
assignee: | nobody → Thomas Herve (therve) |
status: | New → In Progress |
Changed in heat: | |
importance: | Undecided → High |
tags: | added: kilo-backport-potential |
Changed in heat: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-kilo kilo-backport-potential |
Changed in heat: | |
milestone: | liberty-3 → 5.0.0 |
To post a comment you must log in.
From a preliminary study, it seems that as Heat uses ec2 auth for users in a specific domain, it doesn't work anymore on v2.0. Migrating to v3 seems to make the issue goes away, though the token format has changed so it needs to be taken into consideration.
Is the backward incompatible change expected? Is it protecting us from real issues?