Bug 966470 - Keystone Trusts API sends non descriptive error message for requests with invalid trust id
Summary: Keystone Trusts API sends non descriptive error message for requests with inv...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 3.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Nathan Kinder
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-23 10:33 UTC by Pavel Sedlák
Modified: 2016-04-26 22:39 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-01-09 03:23:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1236511 0 None None None Never

Description Pavel Sedlák 2013-05-23 10:33:02 UTC
When request with invalid/not-existing Trust ID is send, the 404 response "message" contains only that ID, not a whole 'sentence' as in other cases.

Discovered with openstack-keystone-2013.1.1-1.el6ost.


Issue request like:
> GET /v3/OS-TRUST/trusts/YOUR_INVALID_ID
or 
> GET /v3/OS-TRUST/trusts/YOUR_INVALID_ID/roles # etc

Reply looks like:
> {u'error': {u'code': 404,
>            u'message': u'YOUR_INVALID_ID',
>            u'title': u'Not Found'}}

For other requests it mostly looks like:
> {u'error': {u'code': 404,
>            u'message': u'Could not find role: b0f22e0104654f5699f801fe90761365',
>            u'title': u'Not Found'}}

So the "Could not find <subject-type>: " part of message is missing here.

Comment 4 Adam Young 2016-01-09 03:23:54 UTC
This will not be changing upstream.


Note You need to log in before you can comment on or make changes to this bug.