Comment 8 for bug 1686597

Michael,

I discovered after investigation that the Mirantis HAPROXY packages is modified to use multiple configuration files stored under /etc/haproxy/conf.d/* . This is not the case in the upstream haproxy package from the UCA repos that wants an unique conf file under /etc/haproxy/haproxy.cfg.

Two questions, first, could you open a bug to modify the configuration of the fuel deployment? it does not make any sense asking the user if wants the package pinned or not to the MOS repos, because it is an obligation to have the MOS package or the deployment fails since the haproxy configuration is written on separate files under conf.d .

The second is, do you know if any other modifications have been done in the MOS haproxy package aside from the reading of the different config files?

Many thanks