[Pacemaker] removing the clone-max restriction messes up my clones

Raoul Bhatia [IPAX] r.bhatia at ipax.at
Fri Feb 27 11:17:39 EST 2009


i had 2 nodes and the following configuration for my clone_webservice
> <nvpair id="clone_webservice_max"      name="clone-max"      value="2" />

i added another node and used cibadmin -D to remove this restriction.
this lead to the following crm_mon output:

> Clone Set: clone_webservice
>     Resource Group: group_webservice:0
>         fs_www:0        (ocf::heartbeat:Filesystem):    Started wc01
>         apache2:0       (ocf::heartbeat:apache):        Started wc02
>     Resource Group: group_webservice:1
>         fs_www:1        (ocf::heartbeat:Filesystem):    Started wc02
>         apache2:1       (ocf::heartbeat:apache):        Started wc02
>     Resource Group: group_webservice:2
>         fs_www:2        (ocf::heartbeat:Filesystem):    Stopped
>         apache2:2       (ocf::heartbeat:apache):        Started wc01

LF Bug #2087

DI (FH) Raoul Bhatia M.Sc.          email.          r.bhatia at ipax.at
Technischer Leiter

IPAX - Aloy Bhatia Hava OEG         web.          http://www.ipax.at
Barawitzkagasse 10/2/2/11           email.            office at ipax.at
1190 Wien                           tel.               +43 1 3670030
FN 277995t HG Wien                  fax.            +43 1 3670030 15

More information about the Pacemaker mailing list