[Pacemaker] crm: timeout for start warning (possible bug?)

[Maros Timko]

>> seems like it is a bit more complicated then I initially though. Now I
>> tried to set the timeout longer so that there will not be any warning.
>> However, the second group is not created neither:
>> # crm
>> crm(live)# configure
>> crm(live)configure# group udom udom-drbd-udom0 udom-drbd-udom1
>> udom-drbd-udom2 udom-delay udom-delay udom-vm \
>
> You are referencing udom-delay _twice_
> I suspect that is the reason for the breakage.
>

You are absolutely right Lars. After this duplication was removed it
works fine in both cases (whether there is a timeout warning or not).
In the meantime I closed the bug that I created yesterday and I
created a new enhancement request for missing warning in such cases.

> I can provoke a very similar "crash" by doing
>
>        primitive dum0 ocf:pacemaker:Dummy
>        primitive dum1 ocf:pacemaker:Dummy
>        primitive dum2 ocf:pacemaker:Dummy
>
>        group gDum dum0 dum1 dum1 dum2
>        delete gDum
>
> if there is no double referencing of dum1,
> it works as expected.
>
> --
> : Lars Ellenberg
> : LINBIT | Your Way to High Availability
> : DRBD/HA support and consulting http://www.linbit.com
>
> DRBD? and LINBIT? are registered trademarks of LINBIT, Austria.
>