When werkzeug was used as the WSGI service for ironic-inspector, it
wrote stack traces to the logs whenever haproxy did a http check; this
listen_options line was the workaround for that. Reverting that change
is done for the following reasons:
- since ironic-inspector now uses oslo-service, the log stack traces
are no longer written
- setting listen_options overrides the default 'option httplog', which is
making diagnosing bug #1854399 harder
- this http-check override may well be the root cause of bug #1854399
(any non-200 response will result in other connections to
ironic-inspector being disconnected?)
Reviewed: https:/ /review. opendev. org/696633 /git.openstack. org/cgit/ openstack/ puppet- tripleo/ commit/ ?id=71abeb12c4d 8106693f0ade7e1 252a00cee0ed56
Committed: https:/
Submitter: Zuul
Branch: master
commit 71abeb12c4d8106 693f0ade7e1252a 00cee0ed56
Author: Steve Baker <email address hidden>
Date: Fri Nov 29 01:01:41 2019 +0000
Remove haproxy ironic-inspector http-check workaround
When werkzeug was used as the WSGI service for ironic-inspector, it
wrote stack traces to the logs whenever haproxy did a http check; this
listen_options line was the workaround for that. Reverting that change
is done for the following reasons:
- since ironic-inspector now uses oslo-service, the log stack traces inspector being disconnected?)
are no longer written
- setting listen_options overrides the default 'option httplog', which is
making diagnosing bug #1854399 harder
- this http-check override may well be the root cause of bug #1854399
(any non-200 response will result in other connections to
ironic-
Change-Id: I5c397d31650b24 8660a39e028c98c 779871d07ba
Partial-Bug: #1854399
Related-Bug: #1691971