Re,
I've just had 2 orphans (tom-DNS:2,tom-DNS:3) for a clone containing 2
groups (tom-DNS:0, tom-DNS:1). Anyway the situation is far better than
before, no more craziness during cleanups. I will dig and test more
tomorrow and give you an update to see if I can reproduce the issue.
1. I was wo
Hey Dejan,
[..] Does "updated" mean deleted now ? :)
"update" doesn't sound like "delete" to me :)
It was a jibe :)
That's really strange since crm doesn't depend on any internal
business of CRM.
Remember, I'm using the latest pacemaker version as suggested by Andrew
to fix some of my clone
On Wed, Jan 06, 2010 at 09:02:07PM +0100, Lars Ellenberg wrote:
> On Wed, Jan 06, 2010 at 10:52:41AM -0500, Frank DiMeo wrote:
> > When I remove the target-role=master specifier from the configuration,
> > and then put the node where the master resources are running into
> > standby, the resources
On Wed, Jan 06, 2010 at 10:52:41AM -0500, Frank DiMeo wrote:
> When I remove the target-role=master specifier from the configuration,
> and then put the node where the master resources are running into
> standby, the resources on the remaining node do not get promoted to
> the master state. Only w
When I remove the target-role=master specifier from the configuration, and then
put the node where the master resources are running into standby, the resources
on the remaining node do not get promoted to the master state. Only with this
specifier included will the slaves be promoted to master
Hi,
On Wed, Jan 06, 2010 at 03:35:10PM +1000, Thomas Guthmann wrote:
> Hi Andrew
>
> >Any chance you could download the latest tarball and try that?
> >
> > http://hg.clusterlabs.org/pacemaker/stable-1.0/archive/1aa7cf1450e4.tar.bz2
>
> Awesome! No more orphans ! \o/
> Everything is working
