Hi,
On Sun, Mar 13, 2011 at 11:15:25PM +0300, Pavel Levshin wrote:
> Hi.
>
> You have hit this:
>
> Mar 3 16:49:16 breadnut2 VirtualDomain[20709]: INFO: Virtual domain vg.test1
> currently has no state, retrying.
> Mar 3 16:49:16 breadnut2 lrmd: [20694]: WARN: p-vd_vg.test1:monitor process
> (
Hi.
You have hit this:
Mar 3 16:49:16 breadnut2 VirtualDomain[20709]: INFO: Virtual domain vg.test1
currently has no state, retrying.
Mar 3 16:49:16 breadnut2 lrmd: [20694]: WARN: p-vd_vg.test1:monitor process
(PID 20709) timed out (try 1). Killing with signal SIGTERM (15).
Mar 3 16:49:16
On Thu, Mar 3, 2011 at 7:05 AM, AP wrote:
> Hi,
>
> Having deep issues with my cluster setup. Everything works ok until
> I add a VirtualDomain RA in. Then things go pearshaped in that it seems
> to ignore the "order" crm config for it and starts as soon as it can.
>
> The crm config is provided b
On Thu, Mar 03, 2011 at 07:45:06AM -0700, Tim Serong wrote:
> Does it behave any differently if you remove the above two constraints, and
> replace them with something like the following (more verbose, but should do
> what you want, assuming I didn't make any typos):
>
> colocation vd-with-libvi
On 3/3/2011 at 05:05 PM, AP wrote:
> Hi,
>
> Having deep issues with my cluster setup. Everything works ok until
> I add a VirtualDomain RA in. Then things go pearshaped in that it seems
> to ignore the "order" crm config for it and starts as soon as it can.
>
> The crm config is provided
Hi,
Having deep issues with my cluster setup. Everything works ok until
I add a VirtualDomain RA in. Then things go pearshaped in that it seems
to ignore the "order" crm config for it and starts as soon as it can.
The crm config is provided below. Basically p-vd_vg.test1 attempts to
start despite
