The problem here is that corosync and pacemaker take control of the execution of the haproxy process - so even if the principle charm stops and disables haproxy, pacemaker will just restart it again; really the stop/disable should happen in the pacemaker layer for processes that it is taking control of.
The problem here is that corosync and pacemaker take control of the execution of the haproxy process - so even if the principle charm stops and disables haproxy, pacemaker will just restart it again; really the stop/disable should happen in the pacemaker layer for processes that it is taking control of.