On 2008-07-24T16:29:54, Gerard Petersen <[EMAIL PROTECTED]> wrote:
> The third node is already added to heartbeat config, and in standby mode.
> We have contraints in place (full log and config will follow), that work
> with the +INF, 'zero' and -INF values, respectively as Master location,
> Slave location and 'Never' location constraints.
>
> When we take the third node online, where the current XenU's according to
> the constraints are not allowed, the resources somehow all are moved to
> the third node, where no xen or drbd is present yet. It seems some of the
> constraints are completely ignored. We have tried this, among other
> things, with the symmetric_cluster value True and False, but no luck.
The problem was that the Xen RA did not actually verify whether the "xm"
command was present, causing misbehaviour.
This is fixed with the RA from dev now.
Regards,
Lars
--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
