Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 966470

Summary: Keystone Trusts API sends non descriptive error message for requests with invalid trust id
Product: Red Hat OpenStack Reporter: Pavel Sedlák <psedlak>
Component: openstack-keystoneAssignee: Nathan Kinder <nkinder>
Status: CLOSED NOTABUG QA Contact: Kaushik Banerjee <kbanerje>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.0CC: ayoung, bsettle, kbanerje, nkinder
Target Milestone: ---Keywords: Automation, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-09 03:23:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.