Bug 964981
Summary: | HTTP 500 when passing "enabled":"true" to keystone | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Jaroslav Henner <jhenner> |
Component: | openstack-keystone | Assignee: | Adam Young <ayoung> |
Status: | CLOSED ERRATA | QA Contact: | Jeremy Agee <jagee> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 3.0 | CC: | apevec, ayoung, dpal, jagee, jhenner, jkt, kbanerje |
Target Milestone: | beta | Keywords: | Triaged |
Target Release: | 4.0 | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2013.2-0.11.b3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-20 00:02:51 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Jaroslav Henner
2013-05-20 08:56:50 UTC
Works with "enabled": true as documented in http://docs.openstack.org/api/openstack-identity-service/2.0/content/POST_addTenant_v2.0_tenants_Admin_API_Service_Developer_Operations-d1e1356.html $ curl -i http://localhost:35357/v2.0/tenants t-type: application/json' -H "Accept: application/json" -H "X-Auth-Token: d55a0d7fca2f47189b199f0c06af2bce" --data '{"tenant": {"enabled": true, "name": "TestServerDiskConfig201853-tenant", "description": "TestServerDiskConfig201853-tenant-desc"}}' HTTP/1.1 200 OK Vary: X-Auth-Token Content-Type: application/json Content-Length: 173 Date: Wed, 22 May 2013 18:27:41 GMT {"tenant": {"description": "TestServerDiskConfig201853-tenant-desc", "enabled": true, "id": "10ac412c38664cd2b425df289ce41c28", "name": "TestServerDiskConfig201853-tenant"}} Please file an upstream bug and link. Seems like it was fixed in Havana. Auto adding >= MODIFIED bugs to beta when "enabled": "true" or "enabled": "false" are submitted. curl -X POST http://localhost:35357/v2.0/tenants -H "content-type: application/json" -H "X-Auth-Token:$TEST_TOKEN" --data '{"tenant": {"enabled": "true", "name": "project", "description": "new project description"}}' Keystone now report: {"error": {"message": "Project enabled is not a boolean", "code": 400, "title": "Bad Request"}} Documented method still functions as expected. curl -X POST http://localhost:35357/v2.0/tenants -H "content-type: application/json" -H "X-Auth-Token:$TEST_TOKEN" --data '{"tenant": {"enabled": true, "name": "myproject1", "description": "new myproject1"}}' {"tenant": {"description": "new myproject1", "enabled": true, "id": "31a977aa9982408d942901ed13d1c31c", "name": "myproject1"}} curl -X POST http://localhost:35357/v2.0/tenants -H "content-type: application/json" -H "X-Auth-Token:$TEST_TOKEN" --data '{"tenant": {"enabled": false, "name": "myproject2", "description": "new myproject2"}}' {"tenant": {"description": "new myproject2", "enabled": false, "id": "19657c0555b74004a8bc28b7f95000df", "name": "myproject2"}} Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHEA-2013-1859.html |