[Pacemaker] crm configure load update

[Dejan Muhamedagic]

Hi,

On Tue, Jan 18, 2011 at 03:35:15PM +0200, Vladislav Bogdanov wrote:
> Hi all,
> 
> It looks like configuration lines are pushed to running CIB line-by-line
> during 'crm configure load update', rather then edit-all/commit.
> 
> I just observed this while pushing dozen of new primitives together with
> colocation/order constraints - primitives tried to start (and failed) on
> a node where constraints are not satisfied.
> 
> Dejan, you should know, is this true?

No, it shouldn't be so, but I'm not sure. The earlier commit
procedure has been quite complex (unnecessarily), and it's still
sometimes in use in pacemaker 1.0.x. Is that the version you're
running?

Anyway, if you don't find any problem with your configuration,
then please open a bugzilla and attach the current configuration
and the configuration you're trying to load.

Cheers,

Dejan

> Is there any workaround (I primarily can not define primitives with
> target-role="Stopped", because configuration could be just an update to
> already-running resource)?
> 
> Best,
> Vladislav
> 
> _______________________________________________
> 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