yahoo-eng-team team mailing list archive

[OpenStack Infra <1726736@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/514810
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=dd473ce7ecb2636ec0a06d31c6211ee113fa2840
Submitter: Zuul
Branch:    master

commit dd473ce7ecb2636ec0a06d31c6211ee113fa2840
Author: Colleen Murphy <colleen@xxxxxxxxxxx>
Date:   Tue Oct 24 21:54:14 2017 +0200

    Remove "no auth token" debug log
    
    When things go badly and we turn on debug logs, we start seeing this
    message about a missing auth token for every auth request. To the
    untrained eye, it looks like the culprit when you are debugging auth
    problems. In reality, it usually just means the initial POST
    /auth/tokens request was sent, which does not include the X-Auth-Token
    header. This log adds more confusion than clarify, so this patch removes
    itin favor of a code comment.
    
    Change-Id: I4657523a170607d664b73ac1f1ab44d7f1460b33
    Closes-bug: #1726736


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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1726736

Title:
  "no auth token" debug logs are confusing

Status in OpenStack Identity (keystone):
  Fix Released

Bug description:
  When things go wrong and the regular info-level logs are not
  informative enough, it is common to turn on debug logging to see
  what's up. When we do that, we see this message spamming the logs for
  auth requests:

  "There is either no auth token in the request or the certificate
  issuer is not trusted. No auth context will be set."

  It's actually a benign message but its meaning is totally unclear and
  to the untrained eye it looks like the cause of auth problems. We
  should either get rid of the message or reword it to make it clear
  what it means.

  It looks like it's perhaps a holdover from the PKI days and could just
  be removed but I'm not sure.

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