[tripleo-heat-templates] haproxy option added for controller caused noisy debug log in keystone

Bug #1405513 reported by Zhenzan Zhou on 2014-12-25
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Low
Unassigned

Bug Description

In controller.yaml, an option "option httpchk GET /" is added in haproxy.cfg for keystone services. The attempt to access this URI will cause keystone to respond a HTTP 300 error message. When Debug is turned on, keystone.log has lots of noisy logs every two seconds, e.g.

Dec 24 16:37:06 allinonecloud-controller0-ryuzcd5cr22o keystone: 2014-12-24 16:37:06.151 5922 DEBUG keystone.common.wsgi [-] arg_dict: {} __call__ /opt/stack/venvs/keystone/local/lib/python2.7/site-packages/keystone/common/wsgi.py:192
Dec 24 16:37:06 allinonecloud-controller0-ryuzcd5cr22o keystone: 2014-12-24 16:37:06.153 5922 INFO eventlet.wsgi.server [-] 30.168.98.168 - - [24/Dec/2014 16:37:06] "GET / HTTP/1.0" 300 925 0.002189
Dec 24 16:37:08 allinonecloud-controller0-ryuzcd5cr22o keystone: 2014-12-24 16:37:08.155 5915 DEBUG keystone.common.wsgi [-] arg_dict: {} __call__ /opt/stack/venvs/keystone/local/lib/python2.7/site-packages/keystone/common/wsgi.py:192
Dec 24 16:37:08 allinonecloud-controller0-ryuzcd5cr22o keystone: 2014-12-24 16:37:08.157 5915 INFO eventlet.wsgi.server [-] 30.168.98.168 - - [24/Dec/2014 16:37:08] "GET / HTTP/1.0" 300 925 0.002304

Ben Nemec (bnemec) wrote :

It looks like this is just because Keystone logs all requests in debug mode. Other than making it possible to sanely not run in debug mode I'm not sure how much we can do about this. I'm also not sure haproxy is the problem - on a production cloud you'd likely be getting as many or more real requests that would also get logged like this.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Low

This bug was reported against an old version of TripleO, and may no longer be valid.

Since it was reported before the start of the liberty cycle (and our oldest stable
branch is stable/liberty), I'm marking this incomplete.

Please reopen this (change the status from incomplete) if the bug is still valid
on a current supported (stable/liberty, stable/mitaka or trunk) version of TripleO,
thanks!

Changed in tripleo:
status: Triaged → Incomplete
Launchpad Janitor (janitor) wrote :

[Expired for tripleo because there has been no activity for 60 days.]

Changed in tripleo:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers