Difference in Implied Roles check API return code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Invalid
|
High
|
Morgan Fainberg |
Bug Description
The Implied Roles check API (HEAD /v3/roles/
- example of output in ubuntu-trusty job:
This bug is not related if returning a 200 or 204 is correct for the given API, but related to the difference between two Ubuntu versions. Additionally, this specific API doesn't use the "wsgi.render_
[1] https:/
[2] https:/
description: | updated |
Changed in keystone: | |
milestone: | next → none |
description: | updated |
Changed in keystone: | |
assignee: | nobody → sonu (sonu-bhumca11) |
Changed in keystone: | |
assignee: | sonu (sonu-bhumca11) → nobody |
Do we have a list of methods that are incorrectly returning 200 instead of 204 in keystone?
From the test "Unexpected http success status code 200, The expected status code is 204"