Red Hat Bugzilla – Bug 1561199
[OSP13] Make HAProxy's stats socket accessible from the host
Last modified: 2018-06-27 09:50:26 EDT
Description of problem: In non-containerized overcloud, we used to have access to HAProxy's stats socket, which allows to retrieve statistics about proxied traffic, current state of backends... In OSP12, this stat socket is not exposed to the host because there is no bind mount configured at container creation. This stats socket should be re-exposed in OSP13, and major upgrade from OSP12 to OSP13 should update the pacemaker bundles accordingly. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy OSP12 2. Upgrade to OSP13 3. Actual results: no stats socket accessible from the host Expected results: stats socket should be available in /var/lib/haproxy/stats Additional info: this bz includes fixes for tripleo-heat-templates and and puppet-tripleo
Verified on OSP13 fresh deployment: openstack-tripleo-heat-templates-8.0.2-4.el7ost.noarch puppet-tripleo-8.3.2-4.el7ost.noarch docker inspect 189f240acf43 . . . "Mounts": [ { "Type": "bind", "Source": "/var/lib/haproxy", "Destination": "/var/lib/haproxy", "Mode": "rw", "RW": true, "Propagation": "rprivate"
Verified on upgraded deployment from OSP12 to OSP13. [root@controller-0 heat-admin]# echo "show info;show stat" | nc -U /var/lib/haproxy/stats | wc -l 143 [root@controller-0 heat-admin]# hostname controller-0 [root@controller-0 heat-admin]# echo "show info;show stat" | nc -U /var/lib/haproxy/stats | wc -l 143 [root@controller-0 heat-admin]# echo "show info;show stat" | nc -U /var/lib/haproxy/stats | tail -n5 swift_proxy_server,controller-0.storage.localdomain,0,0,0,0,,0,0,0,,0,,0,0,0,0,UP,1,1,0,10,2,21349,58,,1,20,1,,0,,2,0,,0,L7OK,200,1,,,,,,,0,,,,0,0,,,,,-1,OK,,0,0,0,0, swift_proxy_server,controller-1.storage.localdomain,0,0,0,0,,0,0,0,,0,,0,0,0,0,UP,1,1,0,10,2,21371,50,,1,20,2,,0,,2,0,,0,L7OK,200,1,,,,,,,0,,,,0,0,,,,,-1,OK,,0,0,0,0, swift_proxy_server,controller-2.storage.localdomain,0,0,0,0,,0,0,0,,0,,0,0,0,0,UP,1,1,0,10,2,21349,48,,1,20,3,,0,,2,0,,0,L7OK,200,1,,,,,,,0,,,,0,0,,,,,-1,OK,,0,0,0,0, swift_proxy_server,BACKEND,0,0,0,0,410,0,0,0,0,0,,0,0,0,0,UP,3,3,0,,2,21371,24,,1,20,0,,0,,1,0,,0,,,,,,,,,,,,,,0,0,0,0,0,0,-1,,,0,0,0,0,
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2018:2086