[Pacemaker] crm resource restart doesn't restart the correct resource

[Dejan Muhamedagic]

Hi,

On Fri, Nov 26, 2010 at 10:43:07AM +0100, Uwe Grawert wrote:
> Zitat von Dejan Muhamedagic <dejanmm at fastmail.fm>:
> >crm resource restart is broken. It just won't work for groups.
> >The restart is actually a stop followed by start. The start
> >precludes the stop of all but the first resource. It will have to
> >be synchronous, that is to wait for all resources to stop first,
> >then to start them. We'll fix it, just didn't get around yet to
> >do that.
> 
> Is that also true for clones? I encounter a problem when setting up
> a group and putting that group into a clone. Until creation of the
> group everything runs fine. But when creating the clone I get an
> orphan of the first primitive in the group and the whole group does
> not run up.

The issue discussed in this thread is the crm shell resource
restart command. Yours is a different matter.

> This is happening, because, when the clone is created,
> pacemaker stops the primitive but does not wait for the stop action
> to return, and just starts the primitive over. And that off course
> causes problems.

Hmm, don't quite understand what is going on. Is that primitive
part of the group? Can you describe in more detail what is going
on.

Thanks,

Dejan

> 
> 
> 
> _______________________________________________
> 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