Only impacts trusty; all other series have the later version of the fix for bug 1481737
-- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1526271 Title: Could not patch cib; leading to no haproxy running Status in haproxy package in Ubuntu: Fix Released Status in haproxy source package in Trusty: In Progress Status in haproxy source package in Vivid: Invalid Status in haproxy source package in Wily: Invalid Status in haproxy source package in Xenial: Fix Released Status in hacluster package in Juju Charms Collection: Invalid Bug description: 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 Error looks remarkably similar to https://bugs.launchpad.net/fuel/+bug/1363908 where they moved away from using crm: "We need to use cibadmin -P instead of crm to avoid such problems as it can lead to cluster in unconfigured state and to following problems with cluster scalability and failover." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1526271/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-ha Post to : [email protected] Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
