[Pacemaker] crm configure update and properties

[Dejan Muhamedagic]

Hi,

On Fri, Jul 09, 2010 at 09:53:04PM -0400, Vadym Chepkov wrote:
> Hi,
> 
> I am not sure if it's a bug or not, but certainly not a pleasant feature.
> At first I configured cluster with property
> stonith-enabled="false", because I didn't have a stontih device handy.
> Then, after I got an APC PDU, I created a separate configuration:
> 
> # cat pdu.crm
> 
> property stonith-enabled="true" stonith-timeout="30s"
> primitive pdu stonith:external/rackpdu \
>         params pduip="10.6.6.6" community="666" hostlist="AUTO" \
>         op start timeout="60s" \
>         meta target-role="Started"
> 
> and loaded it (or so I thought) with
> 
> # crm configure load update pdu.crm
> 
> To my surprise this has removed any other properties my cluster has had :(
> Is it expected behavior? 

It is, I think. A set of properties is just an element, like a
primitive, etc. Though I can see why you find it unexpected. Can
you please open a bugzilla and I'll see if I can fix that.

Thanks,

Dejan

> pacemaker-1.0.9.1
> 
> Thank you,
> Vadym Chepkov
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker