yahoo-eng-team team mailing list archive

[OpenStack Infra <1359995@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/116133
Committed: https://git.openstack.org/cgit/openstack-dev/devstack/commit/?id=2a6ce7197e5da9fddddaba2faff2a18c04ece957
Submitter: Jenkins
Branch:    master

commit 2a6ce7197e5da9fddddaba2faff2a18c04ece957
Author: Brant Knudson <bknudson@xxxxxxxxxx>
Date:   Thu Aug 21 18:23:12 2014 -0500

    Change httpd Keystone access log to keystone_access.log
    
    Keystone's access log was going to httpd/access.log, which is the
    common place for all access logging. This made it difficult to see
    Keystone accesses apart from other access. Keystone's access log
    will now be keystone_access.log
    
    This makes the Keystone configuration similar to Horizon which uses
    horizon_access.log.
    
    Change-Id: I6e5ac121302b3d138758e6c49dffa9f05ad2fb85
    Partial-Bug: #1359995


** Changed in: devstack
       Status: In Progress => Fix Released

-- 
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:
  New

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