[Pacemaker] crm shell - 'location' configuration with multiple id-ref

[Kazunori INOUE]

Hi Dejan,

I reported it in Bugzilla. Please confirm it.
http://developerbugs.linux-foundation.org/show_bug.cgi?id=2602

Best Regards,
Kazunori INOUE

(2011/06/10 17:57), Dejan Muhamedagic wrote:
> Hi,
>
> On Fri, Jun 10, 2011 at 04:22:00PM +0900, Kazunori INOUE wrote:
>> Hi all,
>>
>> I loaded 'location' that specified two id-ref.
>> However, transition processing is not finished.
>>
>> # cat test.crm
>> property no-quorum-policy="ignore" \
>>          stonith-enabled="false" startup-fencing="false"
>> primitive prmDummy1 ocf:pacemaker:Dummy
>> primitive prmDummy2 ocf:pacemaker:Dummy
>> location rsc_location-prmDummy1-1 prmDummy1 \
>>          rule $id="r1" -inf: not_defined attr1 \
>>          rule $id="r2" -inf: not_defined attr2
>>
>> location rsc_location-prmDummy2-2 prmDummy2 \
>>          rule $id-ref="r1" \
>>          rule $id-ref="r2"
>> # crm configure load update test.crm
>> #
>>
>> Please see the attached log.
>>   - Time to have executed loading is about 13:04:13
>>   - It's log of Pacemaker-Devel + Corosync-1.3.0
>>
>>     (The same thing happens with the Heartbeat-3.0.4 stack.)
>>
>> Is it wrong usage?
>
> The usage seems fine. Just tried it and pacemaker gets thoroughly
> confused. Can you please prepare a hb_report and open a bugzilla.
> Try to pinpoint first which element makes the issue reproduce.
> For instance, first commit just the two primitives, then commit
> the first location constraint, then the second. Please turn
> debug off beforehand.
>
> Cheers,
>
> Dejan
>
>> Regards,
>> Kazunori INOUE