[Pacemaker] Order rule added with "crm configure" is truncated

[Superkikim]

Hi,

Thank you for your answer.

How can I update the CRM shell ? I use heartbeat 2.99.2 and Pacemaker 1.0.1.
Is the shell independent from the Pacemaker package ?

-----Original Message-----
From: pacemaker-bounces at clusterlabs.org
[mailto:pacemaker-bounces at clusterlabs.org] On Behalf Of Dejan Muhamedagic
Sent: mardi 16 décembre 2008 14:55
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] Order rule added with "crm configure" is truncated

Hi,

On Sun, Dec 14, 2008 at 12:17:47AM +0100, Superkikim wrote:
> Hi,
> 
>  
> 
> I'm trying to use Pacemaker to implement a cluster. For now, I'm just
trying
> to handle the drbd device. Later, I will add scripts for VMWare Server.
> 
>  
> 
> I followed the document at
>
http://www.clusterlabs.org/mw/DRBD_HowTo_1.0#Configuring_the_resource_in_the
> _CIB. It's quite clear and simple. 
> 
>  
> 
> But when I get to the order rule, I get some problems:
> 
>  
> 
> Configuration before I add the "order" constrain:
> 
>  
> 
> primitive da01 ocf:heartbeat:drbd \
> 
>         params drbd_resource="da01" \
> 
>         operations $id="da01-ops" \
> 
>         op monitor interval="59s" role="Master" timeout="30s" \
> 
>         op monitor interval="60s" role="Slave" timeout="30s"
> 
> primitive da01fs ocf:heartbeat:Filesystem \
> 
>         params fstype="ext3" directory="/vms/da01" device="/dev/drbd6" \
> 
>         meta target-role="Started"
> 
> group da01-group da01fs
> 
> ms ms-da01 da01 \
> 
>         meta clone-max="2" notify="true" globally-unique="false"
> target-role="Stopped"
> 
>  
> 
> Verify does not give an error, except the fact I'm not using stonish.
> 
>  
> 
> Then, I add:
> 
>  
> 
> order ms-da01-before-da01-group mandatory: ms-da01:promote
da01-group:start
> 
>  
> 
> And the result in show is:
> 
>  
> 
> primitive da01 ocf:heartbeat:drbd \
> 
>         params drbd_resource="da01" \
> 
>         operations $id="da01-ops" \
> 
>         op monitor interval="59s" role="Master" timeout="30s" \
> 
>         op monitor interval="60s" role="Slave" timeout="30s"
> 
> primitive da01fs ocf:heartbeat:Filesystem \
> 
>         params fstype="ext3" directory="/vms/da01" device="/dev/drbd6" \
> 
>         meta target-role="Started"
> 
> group da01-group da01fs
> 
> ms ms-da01 da01 \
> 
>         meta clone-max="2" notify="true" globally-unique="false"
> target-role="Stopped"
> 
> order ms-da01-before-da01-group INFINITY:
> 
>  
> 
> Then, I get an error with verify: 
> 
>  
> 
> ERROR: object cli-prefer-ms-da01 cannot be represented in the CLI notation
> 
> ERROR: object ms-da01-before-da01-group cannot be represented in the CLI
> notation
> 
>  
> 
> The question is: Why the "order" rule is truncated and replaced  ?
> 

It was a bug in the crm shell. Fixed recently. You'll have to
upgrade or install the new crm at least.

Thanks,

Dejan

> If I delete ms-da01-before-da01-group, both error messages get away.
> 
>  
> 
> Any help welcome.
> 
>  
> 
> Regards
> 
>  
> 
> Akim
> 

> _______________________________________________
> Pacemaker mailing list
> Pacemaker at clusterlabs.org
> http://list.clusterlabs.org/mailman/listinfo/pacemaker


_______________________________________________
Pacemaker mailing list
Pacemaker at clusterlabs.org
http://list.clusterlabs.org/mailman/listinfo/pacemaker
No virus found in this incoming message.
Checked by AVG - http://www.avg.com 
Version: 8.0.176 / Virus Database: 270.9.18/1848 - Release Date: 15.12.2008
17:04