Bug 1584570 - [UPGRADES] - Tempest reports failure with different expected return code
Summary: [UPGRADES] - Tempest reports failure with different expected return code
Keywords:
Status: CLOSED DUPLICATE of bug 1478168
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-keystone
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Harry Rybacki
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-31 08:44 UTC by Amit Ugol
Modified: 2018-06-07 19:17 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-06-07 19:17:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Amit Ugol 2018-05-31 08:44:45 UTC
Description of problem:

Seen in tempest after upgrading from 12 to 13 (not sure if upgrade related), a test fails with wrong return code. The effect is mostly noise:

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/tempest/api/identity/admin/v3/test_roles.py", line 208, in test_implied_roles_create_check_show_delete
    prior_role_id, implies_role_id)
  File "/usr/lib/python2.7/site-packages/tempest/lib/services/identity/v3/roles_client.py", line 233, in check_role_inference_rule
    self.expected_success(204, resp.status)
  File "/usr/lib/python2.7/site-packages/tempest/lib/common/rest_client.py", line 261, in expected_success
    raise exceptions.InvalidHttpSuccessCode(details)
tempest.lib.exceptions.InvalidHttpSuccessCode: The success code is different than the expected one
Details: Unexpected http success status code 200, The expected status code is 204


Version-Release number of selected component (if applicable):


How reproducible: 100%


Steps to Reproduce:
1. Run tempest on latest working osp13

Comment 2 Harry Rybacki 2018-06-07 19:17:20 UTC
This is a duplicate of rhbz#1478168. Per comments there[1], it is an issue with the version of mod_wsgi being used.  When mod_wsgi is updated in RHEL (as mentioned in comment#2), the expected response will be returned.

[1] - https://bugzilla.redhat.com/show_bug.cgi?id=1478168#c2

*** This bug has been marked as a duplicate of bug 1478168 ***


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