[Pacemaker] crm_attribte failed with Multiple attributes match

[Andrew Beekhof]

On Thu, Jan 7, 2010 at 10:44 PM, hj lee <kerdosa at gmail.com> wrote:
>
>
> On Thu, Jan 7, 2010 at 12:49 PM, hj lee <kerdosa at gmail.com> wrote:
>>
>>
>> On Thu, Jan 7, 2010 at 5:24 AM, Andrew Beekhof <andrew at beekhof.net> wrote:
>>>
>>> On Wed, Jan 6, 2010 at 3:09 AM, hj lee <kerdosa at gmail.com> wrote:
>>> > Hi,
>>> >
>>> > I have a very simple master/slave in two node cluster. The
>>> > crm_attribute
>>> > failed to master score because find_nvpair_attr() found multiple
>>> > matches.
>>> > But I think that's not possible, there should be always one entry for
>>> > master
>>> > score for each node. I just had one failure today. The log is below. I
>>> > think
>>> > this is a bug somewhere around cib query.
>>>
>>> cibadmin -Ql ???
>>>
>>
>> When I checked the cib, it has only one entry for each host.
>>
>> [root at silverthorne2 tmp]# cibadmin -Ql | grep master-vmrd
>>           <nvpair name="master-vmrd-res:0"
>> id="status-copper2-master-vmrd-res:0" value="5"/>
>>           <nvpair name="master-vmrd-res:1"
>> id="status-copper1-master-vmrd-res:1" value="20000"/>
>
> Either case is a problem. If the cib has two entries per one node, then cib
> update has a problem. If the cib has one entry per node correctly, then cib
> query has a problem.

Can you please provide the _complete_ cib + output for both problems.