no migration-threshold for the haproxy resource

[Andrea Ieri]

Since the metaparameter migration-threshold is left to the default of INFINITY for the haproxy resource, crm will always report all instances as running, even if the haproxy service may not be functional.

How to reproduce:
* block haproxy from running (e.g. service haproxy stop ; chmod -x /usr/sbin/haproxy

Expected result:
* res_neutron_haproxy will be in a stopped state after a few monitoring cycles

Current result:
* res_neutron_haproxy remains in started state, regardless of the value of fail-count

This bug may seem harmless, as separate monitoring should be alerting of haproxy failures, but having resources fail and be marked as stopped in pacemaker is necessary for colocation constraints, as they only apply based on whether a dependent resource is started/stopped, and not just on monitor action failures.

NOTE: I experienced this on neutron-apis, but this bug appears to affect all principal charms