Difference in Implied Roles check API return code

Bug #1660603 reported by Rodrigo Duarte on 2017-01-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Identity (keystone)
High
Unassigned

Bug Description

The Implied Roles check API (HEAD /v3/roles/<role_id>/implies/<role_id>) returns 200 in Ubuntu Trusty and 204 in Ubuntu Xenial, check the jobs results at [1] (both running latest master):

- example of output in ubuntu-trusty job:

http://logs.openstack.org/82/426882/1/check/gate-tempest-dsvm-neutron-full-ubuntu-trusty/d4f9ec8/console.html#_2017-01-30_20_11_54_895227

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_response" method [2] - others APIs that use this method (check grant, for example) don't have this problem.

[1] https://review.openstack.org/#/c/426882/
[2] https://github.com/openstack/keystone/blob/aeb51c84bb92d02715208aa8435aa3fd36564c72/keystone/assignment/controllers.py#L518-L519

description: updated
Steve Martinelli (stevemar) wrote :

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"

Steve Martinelli (stevemar) wrote :

This will have to be fixed once we implement microversions. Which is on the table for Pike.

Changed in keystone:
milestone: none → next
importance: Undecided → High
status: New → Confirmed
Changed in keystone:
milestone: next → none
description: updated
sonu (sonu-bhumca11) on 2018-04-04
Changed in keystone:
assignee: nobody → sonu (sonu-bhumca11)
sonu (sonu-bhumca11) on 2018-06-07
Changed in keystone:
assignee: sonu (sonu-bhumca11) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers