David Ames fda5176bd5 Fix pacemaker down crm infinite loop ... On corosync restart, corosync may take longer than a minute to come up. The systemd start script times out too soon. Then pacemaker which is dependent on corosync is immediatly started and fails as corosync is still in the process of starting. Subsequently the charm would run crm node list to validate pacemaker. This would become an infinite loop. This change adds longer timeout values for systemd scripts and adds better error handling and communication to the end user. Change-Id: I7c3d018a03fddfb1f6bfd91fd7aeed4b13879e45 Partial-Bug: #1654403		2017-01-24 10:55:29 -08:00
..
corosync	HACluster refactoring	2012-12-11 07:54:36 -05:00
corosync.conf	let corosync decide the best bindnetaddr from nodelist in udpu case.	2015-08-11 10:49:42 +09:00
hacluster.acl	[billy-olsen,r=] Include an acl file for corosync containing the hacluster	2015-09-03 17:30:23 -07:00
systemd-overrides.conf	Fix pacemaker down crm infinite loop	2017-01-24 10:55:29 -08:00