Hide Forgot
There is an option that can be defined within Spinal Stack that allows for us to specify the logging destination for HAProxy. Since they have a split control plane, the HAPRoxy logs take on a whole new level of importance in troubleshooting stack issues that occur and to help cut down on the clutter of /var/log/messages that was being created we moved the logging out to its own directory. I cannot recall at this time if there was a puppet class that was predefined that I used in Spinal Stack to be able to do this, but I seem to recall possibly having to create one. If one doesn't exist, then it would be a nice one to have.
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
This bugzilla has been removed from the release and needs to be reviewed and Triaged for another Target Release.
This RFE did not make OSP11. I've reassigned it to Lars Kellogg-Stedman, the UA for the OpsTools DFG.
OSP12 and OSP13 log haproxy separately, so this can be closed. (12 logs to /var/log/pacemaker/bundles/haproxy and 13 logs to /var/log/containers/haproxy)