Keystone doesn't handle UTF8 in exceptions
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Jamie Lennox | ||
Havana |
Fix Released
|
High
|
Jamie Lennox |
Bug Description
Originally reported: https:/
Description of problem:
[root@public-
Unable to communicate with identity service: {"error": {"message": "An unexpected error prevented the server from fulfilling your request. 'ascii' codec can't encode character u'\\u2013' in position 11: ordinal not in range(128)", "code": 500, "title": "Internal Server Error"}}. (HTTP 500)
NB: the "dash" in the name is not an ascii dash. It's something else.
Version-Release number of selected component (if applicable):
openstack-
How reproducible:
Every
Additional info:
Performing the same command on a Folsom cloud works just fine.
Changed in keystone: | |
assignee: | nobody → Jamie Lennox (jamielennox) |
Changed in keystone: | |
importance: | Undecided → High |
tags: | added: havana-backport-potential |
Changed in keystone: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
tags: | removed: havana-backport-potential in-stable-havana |
Changed in keystone: | |
milestone: | icehouse-2 → 2014.1 |
If UTF8 characters are thrown in an exception that is to be propagated to the user the message building will fail resulting in a 5xx error.