test_authentication_for_disabled_user ERROR

Bug #1018635 reported by Jay Pipes
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tempest
Fix Released
High
Jay Pipes

Bug Description

On all recent builds, getting this:

22:26:47 ======================================================================
22:26:47 ERROR: Disabled user's token should not get authenticated
22:26:47 ----------------------------------------------------------------------
22:26:47 Traceback (most recent call last):
22:26:47 File "/opt/stack/tempest/tempest/tests/identity/test_users.py", line 151, in test_authentication_for_disabled_user
22:26:47 self.disable_user(self.data.test_user)
22:26:47 File "/opt/stack/tempest/tempest/tests/identity/base_admin_test.py", line 38, in disable_user
22:26:47 self.client.enable_disable_user(user['id'], False)
22:26:47 File "/opt/stack/tempest/tempest/services/identity/json/admin_client.py", line 155, in enable_disable_user
22:26:47 put_body, self.headers)
22:26:47 File "/opt/stack/tempest/tempest/common/rest_client.py", line 163, in put
22:26:47 return self.request('PUT', url, headers, body)
22:26:47 File "/opt/stack/tempest/tempest/common/rest_client.py", line 226, in request
22:26:47 message = resp_body['computeFault']['message']
22:26:47 KeyError: '\'computeFault\'\n-------------------- >> begin captured logging << --------------------\ntempest.common.rest_client: ERROR: Request URL: http://127.0.0.1:35357/v2.0/users/a692f16dc80547a8a789499cbe7a0f48/enabled\ntempest.common.rest_client: ERROR: Request Body: {"user": {"enabled": false}}\ntempest.common.rest_client: ERROR: Response Headers: {\'date\': \'Wed, 27 Jun 2012 22:26:42 GMT\', \'content-type\': \'application/json\', \'content-length\': \'148\', \'status\': \'500\', \'vary\': \'X-Auth-Token\'}\ntempest.common.rest_client: ERROR: Response Body: {u\'error\': {u\'message\': u"An unexpected error prevented the server from fulfilling your request. \'id\'", u\'code\': 500, u\'title\': u\'Internal Server Error\'}}\n--------------------- >> end captured logging << ---------------------'

Probably due to some recent change in Keystone...

Tags: keystone
Revision history for this message
Jay Pipes (jaypipes) wrote :

So, there's a couple things going on here:

1) The KeyError is masking incorrectly the error. Instead of looking for 'computeFault', Keystone is returning 'error' and 'message'.

2) The call to disable the user is failing.

Jay Pipes (jaypipes)
Changed in tempest:
assignee: nobody → Jay Pipes (jaypipes)
Jay Pipes (jaypipes)
Changed in tempest:
status: Confirmed → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tempest (master)

Fix proposed to branch: master
Review: https://review.openstack.org/9501

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tempest (master)

Reviewed: https://review.openstack.org/9501
Committed: http://github.com/openstack/tempest/commit/edba0620c47049c719c43cbfbee74ebf2519e24a
Submitter: Jenkins
Branch: master

commit edba0620c47049c719c43cbfbee74ebf2519e24a
Author: Jay Pipes <email address hidden>
Date: Sun Jul 8 21:34:36 2012 -0400

    Add skip for disabled user test until associated bug is fixed

    Turns out the PUT /users/<USER_ID/enabled call in Keystone
    admin API extension is broken until the fix for the associated
    bug is in. This adds the skip until that is done.

    Change-Id: Ia5d032ebc68c99c9db40e8d96776d81f61a47aec
    Fixes: LP 1018635

Changed in tempest:
status: In Progress → Fix Committed
Jay Pipes (jaypipes)
Changed in tempest:
status: Fix Committed → Fix Released
Sean Dague (sdague)
Changed in tempest:
milestone: none → havana-3
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.