On Tue, Mar 6, 2012 at 3:53 AM, Florian Haas <flor...@hastexo.com> wrote:
> On Sat, Mar 3, 2012 at 8:14 PM, Florian Haas <flor...@hastexo.com> wrote:
>> In other words, interleave=true is actually the reasonable thing to
>> set on all clone instances by default, and I believe the pengine
>> actually does use a default of interleave=true on defined clone sets
>> since some 1.1.x release (I don't recall which).
>
> I think I have to correct myself here, as a cursory "git log
> --grep=interleave" hasn't turned up anything recent. So I might have
> mis-remembered, which would mean the old interleave=false default is
> still unchanged. Andrew, could you clarify please?
It never became the default.
We do appear to be complaining too early though:
diff --git a/pengine/clone.c b/pengine/clone.c
index 5ff0b02..0b832fc 100644
--- a/pengine/clone.c
+++ b/pengine/clone.c
@@ -1035,7 +1035,7 @@ clone_rsc_colocation_rh(resource_t * rsc_lh,
resource_t * rsc_rh, rsc_colocation
if (constraint->rsc_lh->variant >= pe_clone) {
get_clone_variant_data(clone_data_lh, constraint->rsc_lh);
- if (clone_data->clone_node_max != clone_data_lh->clone_node_max) {
+ if (clone_data_lh->interleave && clone_data->clone_node_max
!= clone_data_lh->clone_node_max) {
crm_config_err("Cannot interleave " XML_CIB_TAG_INCARNATION
" %s and %s because"
" they do not support the same number of"
>
> Cheers,
> Florian
>
> --
> Need help with High Availability?
> http://www.hastexo.com/now
_______________________________________________
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
