Unicode chars in invalid database user passwords leads to 500 error codes instead of 400

Bug #1241877 reported by Tim Simpson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack DBaaS (Trove)
Confirmed
Low
Unassigned

Bug Description

If the call to create a database user is made with an invalid password that also contains unicode, such as the pound sign ("£"), the status code returned is 500 rather than 400.

This is because internally, a BadRequest exception is constructed by taking another exception and wrapping it in "str()". Because unicode errors aren't allowed this ends up leading to a different raised exception, thus the 500 error.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to trove (master)

Fix proposed to branch: master
Review: https://review.openstack.org/52726

Changed in trove:
assignee: nobody → Tim Simpson (tim-simpson)
status: New → In Progress
Changed in trove:
importance: Undecided → Low
Amrith Kumar (amrith)
Changed in trove:
assignee: Tim Simpson (tim-simpson) → nobody
status: In Progress → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.