Response bodies should never contain a backtrace
Bug #955411 reported by
Dolph Mathews
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Medium
|
Dolph Mathews | ||
Bug Description
All errors, expected or otherwise, should be wrapped in a keystone.
The client interprets this class of errors correctly, printing the error message and status code in a user friendly format -- keystone needs to take advantage of that to improve the user experience.
This implies suppressing unexpected backtraces from the API but they must still be properly logged (error level).
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (master) | #1 |
| Changed in keystone: | |
| status: | Confirmed → 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: | |
| status: | Fix Committed → Fix Released |
| Changed in keystone: | |
| milestone: | essex-rc1 → 2012.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/