Hi all, I've got two group of resources, say A and B. A depends on B, so if B isn't up A must NOT be started. This is the situation:
group B Bres1 Bres2 Bres3 colocation B_ON_B_ms-r1 inf: B B_ms-r1:Master order B_AFTER_B_ms-r1 inf: B_ms-r1:promote B:start group A Ares1 Ares2 Ares3 colocation A_ON_A_ms-r0 inf: A A_ms-r0:Master order A_AFTER_A_ms-r0 inf: A_ms-r0:promote A:start order A_AFTER_B inf: B:start A:start In a running configuration everything works fine, all the services switch in case of failures or if I force a manual move. The problem is on startup, because for some reason Pacemaker (1.0.10) start first of all Ares1, that of course fails because B is not started. I think that the last order constraint must obligate A to not start before B is done, but things are not going in this way. What am I missing? Thanks a lot! -- Raoul Scarazzini Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene! [email protected] _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
