HI
As Florian explained, start-delay does not solve the problem
so I workarounded it in another way, but what do you call
exactly "my RA" ? I can't see any link to resource-agent ... ?
I can admit that virsh should not return until the vm is really
started and reachable, but I can't change "virsh" ...
Thanks
Alain Moullé
> Hi
> >
> > I think you're right Florian. So I've workarounded the problem
> > because I can't see where to fix it as long as "virsh start vmname" returns
> > immediately wheres the vm is only "starting" but not yet "started" (not
> > yet reachable by ping) .
> > Any idea to fix this properly would be fine.
> >
> > BTW : is the parameter start-delay for op monitor really deprecated ?
> > where could I have the list of parameters deprecated or always valuable ?
>
>
> Not so much deprecated as discouraged.
> If you need it, it usually means there is something wrong with your RA.
>
>
>> >
>> > Thanks
>> > Alain Moull?
>>
>>> >> IOW: start spins on monitor, and if you have a monitor script defined it
>>> >> must not return 0 unless the virtual domain is effectively up.
>>> >>
>>> >> However, status (but not monitor) returns 0 if the domain has been
>>> >> started as per virsh's perspective, disregarding the monitor script
>>> >> (that's why it's called a _monitor_ script, not a status script).
>>> >>
>>> >> Andrew: how is the RA broken here? Since probe uses monitor, the monitor
>>> >> script does apply to a probe. So that can't be the problem I suppose.
>>> >> But here Alain is talking about a status operation -- where does that
>>> >> come from, and how is it relevant?
>>> >>
>>> >> I'd be happy to fix this if and where it's broken, I just fail to see
>>> >> the breakage here. All insights appreciated.
>>> >>
>>> >> Cheers,
>>> >> Florian
>>>
>> >
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
