Comment 0 for bug 1526271

Using Juju 1.24.7, cs:trusty/hacluster-26, with attached Juju status.

hacluster unit log shows that it failed to configure the no-quorum-policy, which then lead to no haproxy running on the unit which was the leader and has the VIP. The symptom I saw was getting "Connection refused" when talking to the VIP.

2015-12-15 00:19:22 DEBUG juju-log hanode:15: Ready to form cluster - informing peers
2015-12-15 00:19:22 DEBUG juju-log hanode:15: Parsing cluster configuration using rid: ha:26, unit: keystone/0
2015-12-15 00:19:23 DEBUG juju-log hanode:15: Configuring and (maybe) restarting corosync
2015-12-15 00:19:23 INFO juju-log hanode:15: Writing file /etc/default/corosync root:root 444
2015-12-15 00:19:23 INFO juju-log hanode:15: Writing file /etc/corosync/uidgid.d/hacluster root:root 444
2015-12-15 00:19:23 INFO juju-log hanode:15: Writing file /etc/corosync/authkey root:root 400
2015-12-15 00:19:23 INFO juju-log hanode:15: Writing file /etc/corosync/corosync.conf root:root 444
2015-12-15 00:19:23 INFO hanode-relation-changed * Restarting corosync daemon corosync
2015-12-15 00:19:23 INFO hanode-relation-changed notice [MAIN ] Corosync Cluster Engine ('2.3.3'): started and ready to provide service.
2015-12-15 00:19:23 INFO hanode-relation-changed info [MAIN ] Corosync built-in features: dbus testagents rdma watchdog augeas pie relro bindnow
2015-12-15 00:19:23 INFO hanode-relation-changed ...done.
2015-12-15 00:19:28 INFO hanode-relation-changed Starting Pacemaker Cluster Manager: [ OK ]
2015-12-15 00:19:28 DEBUG juju-log hanode:15: Applying global cluster configuration
2015-12-15 00:19:28 DEBUG juju-log hanode:15: Configuring no-quorum-policy to stop
2015-12-15 00:19:28 INFO hanode-relation-changed Call cib_apply_diff failed (-206): Application of an update diff failed
2015-12-15 00:19:28 INFO hanode-relation-changed ERROR: could not patch cib (rc=206)
2015-12-15 00:19:28 INFO hanode-relation-changed INFO: offending xml diff: <diff crm_feature_set="3.0.7">
2015-12-15 00:19:28 INFO hanode-relation-changed <diff-removed>
2015-12-15 00:19:28 INFO hanode-relation-changed <cib epoch="22"/>
2015-12-15 00:19:28 INFO hanode-relation-changed </diff-removed>
2015-12-15 00:19:28 INFO hanode-relation-changed <diff-added>
2015-12-15 00:19:28 INFO hanode-relation-changed <cib epoch="23" num_updates="10" admin_epoch="0" validate-with="pacemaker-1.2" crm_feature_set="3.0.7" cib-last-written="Tue Dec 15 00:19:29 2015" update-origin="juju-machine-0-lxc-8" update-client="cibadmin" have-quorum="1" dc-uuid="1002"/>
2015-12-15 00:19:28 INFO hanode-relation-changed </diff-added>
2015-12-15 00:19:28 INFO hanode-relation-changed </diff>
2015-12-15 00:19:28 INFO hanode-relation-changed
2015-12-15 00:19:28 INFO hanode-relation-changed
2015-12-15 00:19:29 DEBUG juju-log hanode:15: Checking monitor host configuration
2015-12-15 00:19:29 INFO juju-log hanode:15: Disabling STONITH
2015-12-15 00:19:29 DEBUG juju-log hanode:15: Deleting Resources
2015-12-15 00:19:29 DEBUG juju-log hanode:15: Configuring Resources: {'res_ks_eth0_vip': 'ocf:heartbeat:IPaddr2', 'res_ks_haproxy': 'lsb:haproxy'}
2015-12-15 00:19:29 INFO hanode-relation-changed Removing any system startup links for /etc/init.d/haproxy ...
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc0.d/K20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc1.d/K20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc2.d/S20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc3.d/S20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc4.d/S20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc5.d/S20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed /etc/rc6.d/K20haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed * Stopping haproxy haproxy
2015-12-15 00:19:29 INFO hanode-relation-changed ...done.

--

keystone/2 has a running haproxy and is behaving as expected