Comment 18 for bug 1737776

OK, so it looks like there's one more issue which causes the "ha-relation-changed" hook being run: the "json_init_services" keeps being populated with "haproxy" values. Please take a look on the following tries:

TRY 1:

root@juju-baab69-29-lxd-8:/var/lib/juju/agents/unit-designate-hacluster-63/charm# relation-get -r 507 - designate/9
clones: '{''cl_res_designate_haproxy'': ''res_designate_haproxy''}'
corosync_bindiface: eth0
corosync_mcastport: "4440"
groups: '{''grp_designate_vips'': ''res_designate_eth0_vip''}'
init_services: '[''haproxy'']'
json_clones: '{"cl_res_designate_haproxy": "res_designate_haproxy"}'
json_groups: '{"grp_designate_vips": "res_designate_eth0_vip"}'
json_init_services: '["haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
...
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy"]'
json_res_designate_eth0_vip: '"ocf:heartbeat:IPaddr2"'
json_res_designate_haproxy: '"lsb:haproxy"'
json_resource_params: '{"res_designate_eth0_vip": " params ip=\"100.86.0.11\" nic=\"eth0\"
  cidr_netmask=\"255.255.240.0\"", "res_designate_haproxy": " op monitor interval=\"5s\""}'
json_resources: '{"res_designate_eth0_vip": "ocf:heartbeat:IPaddr2", "res_designate_haproxy":
  "lsb:haproxy"}'
private-address: 100.107.2.78
res_designate_eth0_vip: ocf:heartbeat:IPaddr2
res_designate_haproxy: lsb:haproxy
resource_params: '{''res_designate_haproxy'': '' op monitor interval="5s"'', ''res_designate_eth0_vip'':
  '' params ip="100.86.0.11" nic="eth0" cidr_netmask="255.255.240.0"''}'
resources: '{''res_designate_haproxy'': ''lsb:haproxy'', ''res_designate_eth0_vip'':
  ''ocf:heartbeat:IPaddr2''}'

TRY 2:

root@juju-baab69-29-lxd-8:/var/lib/juju/agents/unit-designate-hacluster-63/charm# relation-get -r 507 - designate/9
clones: '{''cl_res_designate_haproxy'': ''res_designate_haproxy''}'
corosync_bindiface: eth0
corosync_mcastport: "4440"
groups: '{''grp_designate_vips'': ''res_designate_eth0_vip''}'
init_services: '[''haproxy'']'
json_clones: '{"cl_res_designate_haproxy": "res_designate_haproxy"}'
json_groups: '{"grp_designate_vips": "res_designate_eth0_vip"}'
json_init_services: '["haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
...
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",
  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy"]'
json_res_designate_eth0_vip: '"ocf:heartbeat:IPaddr2"'
json_res_designate_haproxy: '"lsb:haproxy"'
json_resource_params: '{"res_designate_eth0_vip": " params ip=\"100.86.0.11\" nic=\"eth0\"
  cidr_netmask=\"255.255.240.0\"", "res_designate_haproxy": " op monitor interval=\"5s\""}'
json_resources: '{"res_designate_eth0_vip": "ocf:heartbeat:IPaddr2", "res_designate_haproxy":
  "lsb:haproxy"}'
private-address: 100.107.2.78
res_designate_eth0_vip: ocf:heartbeat:IPaddr2
res_designate_haproxy: lsb:haproxy
resource_params: '{''res_designate_haproxy'': '' op monitor interval="5s"'', ''res_designate_eth0_vip'':
  '' params ip="100.86.0.11" nic="eth0" cidr_netmask="255.255.240.0"''}'
resources: '{''res_designate_haproxy'': ''lsb:haproxy'', ''res_designate_eth0_vip'':
  ''ocf:heartbeat:IPaddr2''}'

Dots ("...") were used to indicate additional lines like the following one:

  "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy", "haproxy",

At the moment in the environment I upgraded there are hundreds of them. Attached is the full output.