keystone reports internal error when policy.json is broken
Bug #1177623 reported by
xingzhou
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
Low
|
Lance Bragstad |
Bug Description
if policy.json is broken, when using keystone apis, will return HTTP 500 (internal error).
For better user experience, we need to provide:
1). a better response for use to explain what had happend
and
2). a default policy list to use in case the policy.json is broken.
Changed in keystone: | |
assignee: | nobody → xingzhou (xingzhou) |
Changed in keystone: | |
status: | Confirmed → In Progress |
Changed in keystone: | |
milestone: | none → kilo-1 |
Changed in keystone: | |
status: | Fix Committed → Fix Released |
Changed in keystone: | |
milestone: | kilo-1 → 2015.1.0 |
To post a comment you must log in.
If policy.json is "broken" (invalid JSON syntax, for example), I'd fully expect the API to return a generic 500. However, an ERROR log explaining that policy.json could not be parsed would certainly be beneficial.