TokenNotFound at WARNING level spamming logs

[John Dennis]

We gotten a number of complaints about client logs filling up with these ominous WARNING messages that make folks think there is something seriously wrong when in fact it's normal token expiration.

WARNING keystonemiddleware.auth_token [-] Authorization failed for token
WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Could not find token: 24ffb14540c74a7c964f9627fe2af8fb", "code": 404, "title": "Not Found"}}

Seemingly nothing fails because of these events so we would like to log these at the INFO level instead of the WARNING level. This will keep the logs smaller and reduce the anxiety of seeing so many WARNING messages.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/528129
Committed: https://git.openstack.org/cgit/openstack/keystonemiddleware/commit/?id=8b648488b226a76e291292fd3387bc7c04b3f24c
Submitter: Zuul
Branch: master

commit 8b648488b226a76e291292fd3387bc7c04b3f24c
Author: John Dennis <email address hidden>
Date: Thu Dec 14 18:39:49 2017 -0500

    Log TokenNotFound at INFO level instead of WARNING

    Token expiration is normal, however the client logs fill up with these
    ominous WARNING messages:

    WARNING keystonemiddleware.auth_token [-] Authorization failed for token
    WARNING keystonemiddleware.auth_token [-] Identity response: {"error": {"message": "Could not find token: 24ffb14540c74a7c964f9627fe2af8fb", "code": 404, "title": "Not Found"}}

    It seems more useful to log normal events at a level less than WARNING,
    this would reduce the log size but more importantly it will help
    elminate the concerns raised when logs are filled with WARNING messages
    that are otherwise benign.

    Change-Id: I54ad6b5530ee81616bd4a44f8295985f5d84c2ee
    Closes-Bug: #1738300
    Signed-off-by: John Dennis <email address hidden>

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/keystonemiddleware 4.21.0 release.