The "enabled" field is not type-safe nor is it normalized
Bug #1023544 reported by
Jay Pipes
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Low
|
Adam Young | ||
Bug Description
Marking a user or tenant enabled using the keystone admin API (with at least the SQL backend) by doing this:
POST /users/
with these payloads:
{'enabled': 'TRUE'}
{'enabled': 'True'}
{'enabled': true}
results in completely different results. This is because enabled is not a real column, as it's locked away in a JSON BLOB.
One ramification of this is that the enabled column in Horizon's users and tenants views shows different cases for the word True or False.
| Changed in keystone: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| Changed in keystone: | |
| assignee: | nobody → Adam Young (ayoung) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (master) | #1 |
| Changed in keystone: | |
| status: | Triaged → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone (master) | #2 |
| Changed in keystone: | |
| status: | In Progress → Fix Committed |
| Changed in keystone: | |
| milestone: | none → grizzly-2 |
| status: | Fix Committed → Fix Released |
| Changed in keystone: | |
| milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/