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>
Reviewed: https:/ /review. openstack. org/528129 /git.openstack. org/cgit/ openstack/ keystonemiddlew are/commit/ ?id=8b648488b22 6a76e291292fd33 87bc7c04b3f24c
Committed: https:/
Submitter: Zuul
Branch: master
commit 8b648488b226a76 e291292fd3387bc 7c04b3f24c
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 keystonemiddlew are.auth_ token [-] Authorization failed for token are.auth_ token [-] Identity response: {"error": {"message": "Could not find token: 24ffb14540c74a7 c964f9627fe2af8 fb", "code": 404, "title": "Not Found"}}
WARNING keystonemiddlew
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: I54ad6b5530ee81 616bd4a44f82959 85f5d84c2ee
Closes-Bug: #1738300
Signed-off-by: John Dennis <email address hidden>