Vadym Chepkov wrote:
> On Nov 24, 2010, at 3:22 PM, Robinson, Eric wrote:
>
>
>>> Nope, this was created by "move"/"migrate" command.
>>> Somebody forgot "unmove"/"unmigrate"
>>>
>> Actually, it wasn't. We pulled the plug on node ha07b, watched the
>> resource failover, and then plugged it back in and watched it fail back.
>> We didn't issue a move command that I recall.
>>
>
>
> I appeal to Dejan here. I am positive "cli-prefer-*" constraints are created
> when crm resource move command is issued.
> You maybe didn't do it this time, but it has been sitting there from some
> time before.
>
> Vadym
>
The crm resource move command creates a cli-standby-* rule:
r...@cluster1:~# crm resource move all
WARNING: Creating rsc_location constraint 'cli-standby-all' with a score
of -INFINITY for resource all on cluster2.
This will prevent all from running on cluster2 until the
constraint is removed using the 'crm_resource -U' command or manually
with cibadmin
This will be the case even if cluster2 is the last node in the
cluster
This message can be disabled with -Q
r...@cluster1:~# crm configure show | grep cli
location cli-standby-all all \
rule $id="cli-standby-rule-all" -inf: #uname eq cluster2
However the cli-prefer-* didn't come from the drbd fencing script. The
fencing script creates a drbd-fence-by-handler-* location constraint, so
it wasn't from this either:
r...@cluster2:~# echo b > /proc/sysrq-trigger
r...@cluster1:~# crm configure show | grep fence
location drbd-fence-by-handler-ms_drbd_home ms_drbd_home \
rule $id="drbd-fence-by-handler-rule-ms_drbd_home"
$role="Master" -inf: #uname ne cluster2
location drbd-fence-by-handler-ms_drbd_mysql ms_drbd_mysql \
rule $id="drbd-fence-by-handler-rule-ms_drbd_mysql"
$role="Master" -inf: #uname ne cluster2
location drbd-fence-by-handler-ms_drbd_storage ms_drbd_storage \
rule $id="drbd-fence-by-handler-rule-ms_drbd_storage"
$role="Master" -inf: #uname ne cluster2
>
>> --
>> Eric Robinson
>>
>>
>> Disclaimer - November 24, 2010
>> This email and any files transmitted with it are confidential and intended
>> solely for General Linux-HA mailing list. If you are not the named addressee
>> you should not disseminate, distribute, copy or alter this email. Any views
>> or opinions presented in this email are solely those of the author and might
>> not represent those of Physicians' Managed Care or Physician Select
>> Management. Warning: Although Physicians' Managed Care or Physician Select
>> Management has taken reasonable precautions to ensure no viruses are present
>> in this email, the company cannot accept responsibility for any loss or
>> damage arising from the use of this email or attachments.
>> This disclaimer was added by Policy Patrol: http://www.policypatrol.com/
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
>
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
--
Dan FRINCU
Systems Engineer
CCNA, RHCE
Streamwide Romania
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
