On 02/16/2017 05:12 PM, Oscar Segarra wrote:
> Sorry, In the other node I get exactly the same log entries:
>
> VirtualDomain(vm-vdicone01)[125890]:2017/02/16_17:11:45 ERROR:
> Configuration file /mnt/nfs-vdic-mgmt-vm/vdicone01.xml does not exist
> or is not readable.
>
Sorry, In the other node I get exactly the same log entries:
VirtualDomain(vm-vdicone01)[125890]:2017/02/16_17:11:45 ERROR:
Configuration file /mnt/nfs-vdic-mgmt-vm/vdicone01.xml does not exist or is
not readable.
VirtualDomain(vm-vdicone01)[125912]:2017/02/16_17:11:45 INFO:
Configuration
Hi Klaus,
I have delted the op stop:
pcs resource op remove vm-vdicone01 stop interval=0s timeout=90
pcs resource op remove vm-vdicdb01 stop interval=0s timeout=90
pcs resource op remove vm-vdicsunstone01 stop interval=0s timeout=90
pcs resource op remove vm-vdicudsserver stop interval=0s
On 02/16/2017 11:02 AM, Oscar Segarra wrote:
> Hi Kaluss
>
> Which is your proposal to fix this behavior?
First you can try to remove the monitor op for role=stopped.
Then the startup-probing will probably still fail but for that
the behaviour is different.
The startup-probing can be disabled
Hi Kaluss
Which is your proposal to fix this behavior?
Thanks a lot!
El 16 feb. 2017 10:57 a. m., "Klaus Wenninger"
escribió:
On 02/16/2017 09:05 AM, Oscar Segarra wrote:
> Hi,
>
> In my environment I have deployed 5 VirtualDomains as one can see below:
>