[Pacemaker] resources not migrating when some are not runnable on one node, maybe because of groups or master/slave clones?

[Phil Frost]

On 06/22/2012 04:40 AM, Andreas Kurz wrote:
>> I took a look at the cib in case2 and saw this in the status for storage02.
>> >
>> >       <transient_attributes id="storage02">
>> >         <instance_attributes id="status-storage02">
>> >           <nvpair id="status-storage02-probe_complete" name="probe_complete" value="true"/>
>> >           <nvpair id="status-storage02-master-drbd_nfsexports.1" name="master-drbd_nfsexports:1" value="10"/>
>> >         </instance_attributes>
>> >       </transient_attributes>
>> >
>> >storage02 will not give up the drbd master since it has a higher score that storage01.  This coupled with the colocation rule between test and the drbd master, and the location rule to never run "test" on storage02 cause the "test" resource to never run.... "test" has to run with the drbd master, and the drbd master is stuck because of the transient attributes on a node "test" can't run on, so "test" can't start.
>> >
>> >I don't understand why the transient attribute is there, or where it came from yet.
> This is added by the RA with the crm_master command. For example the
> drbd RA chooses this value from the current state of drbd to let
> Pacemaker promote best candidate.

I'm not really sure I understand this transient attribute business. Is 
this suggesting there's a configuration problem, or a problem with the 
RA? It looks to me that the colocation constraints aren't being 
considered at all in calculating the promotion scores (at least, that's 
what crm_simulate suggests). Can this transient attribute explain that, 
or is there something else in play?