Description of problem: Can we have [1] backported to OSP10 ? """ It is currently not possible to customize haproxy on a per service basis. There are situations where it would be advantageous to let an operator specify custom per-service options. One such use case seen in the wild is to extend the timeout of the cinder because due to the specific storage backend these cinder operations sometimes take a bit longer. Letting the user tweak the haproxy_default_timeout is likely not what we want as for the case above we only want to tweak a single service. """ [1]https://bugs.launchpad.net/tripleo/+bug/1755711
upstream bz filled and fixed by bandini, so moving from df to pidone as well
Hi, any updates? Thanks
Verified, [stack@undercloud-0 ~]$ cat core_puddle_version 2018-12-13.1[stack@undercloud-0 ~]$ #redeploy with extra configs for custom haproxy params: [stack@undercloud-0 ~]$ diff overcloud_deploy.sh overcloud_deploy.shorg < -e /home/stack/custom_haproxy_timeout.yaml [stack@undercloud-0 ~]$ cat /home/stack/custom_haproxy_timeout.yaml ExtraConfig: tripleo::haproxy::cinder::options: "timeout client": '88m' Stack overcloud CREATE_COMPLETE Overcloud Endpoint: http://10.0.0.105:5000/v2.0 Overcloud Deployed [stack@undercloud-0 ~]$ ansible controller -b -mshell -a'grep 88 /etc/haproxy/haproxy.cfg' [WARNING]: Found both group and host with same name: undercloud controller-0 | SUCCESS | rc=0 >> timeout client 88m timeout server 88m controller-1 | SUCCESS | rc=0 >> timeout client 88m timeout server 88m
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/RHBA-2019:0055