trusts in keystone fail in backend when impersonation is not provided
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Lance Bragstad |
Bug Description
When creating trusts in Keystone, if 'impersonation' is not provided Keystone fails out in the backend code. This should probably be handed at the controller level to be consistent across all backends.
lbragstad@
{
"trust": {
"roles": [
{
}
],
}
}
lbragstad@
{
"trust": {
"roles": [
{
}
],
}
}
Using impersonation in the create_trust.json file returns a trust successfully:
lbragstad@
HTTP/1.1 201 Created
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 675
Date: Sun, 09 Feb 2014 04:36:56 GMT
{"trust": {"impersonation": true, "roles_links": {"self": "http://
When using the request without impersonation defined I get:
lbragstad@
t:5000/
HTTP/1.1 500 Internal Server Error
Vary: X-Auth-Token
Content-Type: application/json
Content-Length: 618
Date: Sun, 09 Feb 2014 04:33:08 GMT
{"error": {"message": "An unexpected error prevented the server from fulfilling your request. (OperationalError) (1048, \"Column 'impersonation
' cannot be null\") 'INSERT INTO trust (id, trustor_user_id, trustee_user_id, project_id, impersonation, deleted_at, expires_at, extra) VALUES
(%s, %s, %s, %s, %s, %s, %s, %s)' ('b49ac0c7558a4
'c7e2b98178e644
code": 500, "title": "Internal Server Error"}}
According to the Identity V3 API, 'impersonation' is a requirement when creating a trust. https:/
summary: |
- trusts in keystone fail in driver when impersonation is not provided + trusts in keystone fail in backend when impersonation is not provided |
description: | updated |
Changed in keystone: | |
assignee: | Lance Bragstad (ldbragst) → Morgan Fainberg (mdrnstm) |
Changed in keystone: | |
assignee: | Morgan Fainberg (mdrnstm) → Lance Bragstad (ldbragst) |
importance: | Undecided → High |
importance: | High → Medium |
Fix proposed to branch: master /review. openstack. org/72582
Review: https:/