Unparseable endpoint URL's should raise a user friendly error
Bug #1058494 reported by
Dolph Mathews
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Identity (keystone) |
Fix Released
|
Undecided
|
stelford | ||
| Folsom |
Fix Released
|
Low
|
Alan Pevec | ||
Bug Description
A common user-error during configuration involves mistakes in the configured endpoint URLs, resulting in failed string formatting. Unfortunately, keystone barfs back a 500 and dumps a rather user-unfriendly stacktrace back to the logs with no real indication of what went wrong.
I think this condition should be caught with the following results:
A) a user-friendly 500 should be raised back to the client, at least suggesting that the user read the logs for more details
B) an ERROR message should be logged with the offending URL, and a note about what was expected of it
Most recently, this came up on the mailing list: https:/
| Changed in keystone: | |
| status: | New → Confirmed |
| Changed in keystone: | |
| assignee: | nobody → stelford (stef-ummon) |
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: | |
| milestone: | none → grizzly-1 |
| status: | Fix Committed → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to keystone (stable/folsom) | #3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to keystone (stable/folsom) | #4 |
| Changed in keystone: | |
| milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/