Horizon and Keystone are having some sort of disagreement about the auth api. 2.0 supports logins but not project info; 3 doesn't work with logins.
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| keystone policy changes: | operations/puppet | production | +7 -7 | |
| Use keystone v3 api for horizon | operations/puppet | production | +5 -1 |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Andrew | T42525 Cant add a security group to an existing instance | |||
| Resolved | Andrew | T87279 Make OpenStack Horizon useful for production labs | |||
| Resolved | Andrew | T124181 Support instance manipulation, proxies, dns with Horizon | |||
| Resolved | Andrew | T123310 Unable to change projects in horizon | |||
| Duplicate | Andrew | T124186 Switch from ldap project assignment to keystone/mysql project assignment | |||
| Resolved | Andrew | T125002 Figure out what to do about servicegrouphomedirpattern |
Event Timeline
Comment Actions
This is because we're currently using the Keystone v3 api, which does not work with ldap assignment.
Comment Actions
Going to triage this as high, because this prevents user to work with horizon, and it is very anoying.
Comment Actions
Change 270593 had a related patch set uploaded (by Andrew Bogott):
Use keystone v3 api for horizon
Comment Actions
Change 270597 had a related patch set uploaded (by Andrew Bogott):
keystone policy changes:
Comment Actions
This is now resolved.
Note that for unrelated reasons I've disabled all nova actions in Horizon, so Horizon is currently useful only for viewing projects. Actions will be re-enabled once we have 2fa logins.