yahoo-eng-team team mailing list archive

[David Kranz <dkranz@xxxxxxxxxx>]

Tempest does check for token expiry and no test should fail due to an
expired token. So this must be a keystone issue. I just looked at
another bug that got an unauthorized for one of the keystone tests with
no explanation which I also added keystone to the ticket
https://bugs.launchpad.net/keystone/+bug/1360504

** Changed in: tempest
       Status: New => Confirmed

** Changed in: tempest
       Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1359995

Title:
  Tempest failed to delete user

Status in devstack - openstack dev environments:
  Fix Released
Status in OpenStack Identity (Keystone):
  Incomplete
Status in Tempest:
  Invalid

Bug description:
  
  check-tempest-dsvm-full failed on a keystone change. Here's the main log: http://logs.openstack.org/73/111573/4/check/check-tempest-dsvm-full/c5ce3bd/console.html

  The traceback shows:

  File "tempest/api/volume/test_volumes_list.py", line 80, in tearDownClass
  File "tempest/services/identity/json/identity_client.py", line 189, in delete_user
  Unauthorized: Unauthorized
  Details: {"error": {"message": "The request you have made requires authentication. (Disable debug mode to suppress these details.)", "code": 401, "title": "Unauthorized"}}

  So it's trying to delete the user and it gets unauthorized. Maybe the
  token was expired or marked invalid for some reason.

  There's something wrong here, but the keystone logs are useless for
  debugging now that it's running in Apache httpd. The logs don't have
  the request or result line, so you can't find where the request was
  being made.

  Also, Tempest should be able to handle the token being invalidated. It
  should just get a new token and try with that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1359995/+subscriptions