On 15/12/14 01:15 AM, Andrew Beekhof wrote:
Just a courtesy email for anyone looking for me or waiting on a reply from me
specifically...
I have been sucked into openstack hell and probably won't re-emerge until early
January at the earliest.
Until then its unlikely that I'll be able to deal w
Just a courtesy email for anyone looking for me or waiting on a reply from me
specifically...
I have been sucked into openstack hell and probably won't re-emerge until early
January at the earliest.
Until then its unlikely that I'll be able to deal with anything except the
lowest of the low han
Hi Andrew,
Frequently one node gets disconnected from CIB and stops the cluster
resources. I'm not able to start or cleanup failed actions for any of the
resources. For ex, if nodeA gets disconnected from CIB, I won't be able to
run actions on a resource like cleanup/stop/restart,... as that hangs
> On 12 Dec 2014, at 9:57 pm, Bharathiraja P wrote:
>
> Hi,
>
> We run pacemaker+corosync cluster on OpenSuSE 13.1 QEMU guests.
>
> Frequently, one node gets disconnected from cib. This is the message seen in
> corosync logs,
>
> Nov 25 08:36:07 [3760] sysmon-secondarycib:debug:
