redis stunnel log level is too high

[Michele Baldessari]

Right now the default stunnel.conf log level is set at 'notice'
which, when we deploy redis, fills up the logs with the following
messages:
May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: connect_blocking: connected 127.0.0.1:6379
May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: Service [redis] connected remote server from 127.0.0.1:60412
May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770
May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770
May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379
May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379
May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418
May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418

Those messages are from the haproxy healthceck. Let's move the
default debug config to warning which will ignore the above errors.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/567250
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=a9c1bc3518750e25d23ec19e592750a8f744e696
Submitter: Zuul
Branch: master

commit a9c1bc3518750e25d23ec19e592750a8f744e696
Author: Michele Baldessari <email address hidden>
Date: Wed May 9 16:17:50 2018 +0200

    Lower the default stunnel log level

    Right now the default stunnel.conf log level is set at 'notice'
    which, when we deploy redis, fills up the logs with the following
    messages:
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: connect_blocking: connected 127.0.0.1:6379
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: Service [redis] connected remote server from 127.0.0.1:60412
    May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770
    May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379
    May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418

    Those messages are from the haproxy healthceck. Let's move the
    default debug config to warning which will ignore the above errors.

    Closes-Bug: #1770180

    Change-Id: I93bd0048e85864fa9e62dc38c3575ec7b48e5df5

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/queens
Review: https://review.openstack.org/571148

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/571148
Committed: https://git.openstack.org/cgit/openstack/puppet-tripleo/commit/?id=0bde3cd3a335639eb1630f170d150be65325d7ee
Submitter: Zuul
Branch: stable/queens

commit 0bde3cd3a335639eb1630f170d150be65325d7ee
Author: Michele Baldessari <email address hidden>
Date: Wed May 9 16:17:50 2018 +0200

    Lower the default stunnel log level

    Right now the default stunnel.conf log level is set at 'notice'
    which, when we deploy redis, fills up the logs with the following
    messages:
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: connect_blocking: connected 127.0.0.1:6379
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682520320]: Service [redis] connected remote server from 127.0.0.1:60412
    May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] accepted connection from 172.17.1.21:60770
    May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: connect_blocking: connected 127.0.0.1:6379
    May 09 14:18:36 controller-1.redhat.local stunnel[41495]: LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418
    May 09 14:18:36 controller-1.redhat.local dockerd-current[19810]: 2018.05.09 14:18:36 LOG5[1:139972682409728]: Service [redis] connected remote server from 127.0.0.1:60418

    Those messages are from the haproxy healthceck. Let's move the
    default debug config to warning which will ignore the above errors.

    Closes-Bug: #1770180

    Change-Id: I93bd0048e85864fa9e62dc38c3575ec7b48e5df5
    (cherry picked from commit a9c1bc3518750e25d23ec19e592750a8f744e696)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-tripleo 9.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-tripleo 8.3.4 release.