On Fri, Oct 12, 2012 at 6:22 PM, Florian Haas wrote:
> On Fri, Oct 12, 2012 at 3:18 AM, Andrew Beekhof wrote:
>> This has been a topic that has popped up occasionally over the years.
>> Unfortunately we still don't have a good answer for you.
>>
>> The "least worst" practice has been to have the
On Fri, 12 Oct 2012 09:22:13 +0200 Florian Haas
wrote:
> For most people, this issue doesn't occur on system boot, as libvirtd
> would normally start before corosync, or corosync/pacemaker isn't part
> of the system bootup sequence at all (the latter is preferred for
> two-node clusters to prevent
On Fri, Oct 12, 2012 at 3:18 AM, Andrew Beekhof wrote:
> This has been a topic that has popped up occasionally over the years.
> Unfortunately we still don't have a good answer for you.
>
> The "least worst" practice has been to have the RA return OCF_STOPPED
> for non-recurring monitor operations
This has been a topic that has popped up occasionally over the years.
Unfortunately we still don't have a good answer for you.
The "least worst" practice has been to have the RA return OCF_STOPPED
for non-recurring monitor operations (aka. startup probes) IFF its
pre-requistites (ie. binaries, or
