crm does not monitor haproxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack HA Cluster Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
The way that hacluster resources are organized allows haproxy to be down on a node whre the VIP is running.
Example configuration:
root@juju-
node 1000: juju-3f2dbe-
node 1001: juju-3f2dbe-
node 1002: juju-3f2dbe-
primitive res_ks_6f94244_vip IPaddr2 \
params ip=172.16.128.9 \
op monitor timeout=20s interval=10s depth=0
primitive res_ks_haproxy lsb:haproxy \
op monitor interval=5s
group grp_ks_vips res_ks_6f94244_vip
clone cl_ks_haproxy res_ks_haproxy
property cib-bootstrap-
rsc_defaults rsc-options: \
There is no collocation stanza that would enforce running VIP only on node where haproxy is running. Example:
clone cl_ks_haproxy res_ks_haproxy
colocation haproxy_6f94244_vip inf: res_ks_6f94244_vip res_ks_haproxy
Changed in charm-hacluster: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Testing confirms it would fail and VIP won't migrate if haproxy is killed and not respawned: https:/ /pastebin. canonical. com/p/QR4fRP4Cc K/
However automatic haproxy restarting mitigates the issue.