[Pacemaker] Pacemaker remote nodes, naming, and attributes

David Vossel dvossel at redhat.com
Fri Jul 5 17:06:16 EDT 2013


----- Original Message -----
> From: "David Vossel" <dvossel at redhat.com>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Wednesday, July 3, 2013 4:20:37 PM
> Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes
> 
> ----- Original Message -----
> > From: "Lindsay Todd" <rltodd.ml1 at gmail.com>
> > To: "The Pacemaker cluster resource manager"
> > <pacemaker at oss.clusterlabs.org>
> > Sent: Wednesday, July 3, 2013 2:12:05 PM
> > Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes
> > 
> > Well, I'm not getting failures right now simply with attributes, but I can
> > induce a failure by stopping the vm-db02 (it puts db02 into an unclean
> > state, and attempts to migrate the unrelated vm-compute-test). I've
> > collected the commands from my latest interactions, a crm_report, and a gdb
> > traceback from the core file that crmd dumped, into bug 5164.
> 
> 
> Thanks, hopefully I can start investigating this Friday
> 
> -- Vossel

Yeah, this is a bad one.  Adding the node attributes using crm_attribute for the remote-node did some unexpected things to the crmd component.  Somehow the remote-node was getting entered into the cluster node cache... which made it look like we had both a cluster-node and remote-node named the same thing... not good.

I think I got that part worked out.  Try this patch.

https://github.com/ClusterLabs/pacemaker/commit/67dfff76d632f1796c9ded8fd367aa49258c8c32

Rather than trying to patch RCs, it might be worth trying out the master branch on github (which already has this patch).  If you aren't already, use rpms to make your life easier.  Running 'make rpm' in the source directory will generate them for you.

There was another bug fixed recently in pacemaker_remote involving the directory created for resource agents to store their temporary data (stuff like pid files).  I believe the fix was not introduced until 1.1.10rc6.

-- Vossel





More information about the Pacemaker mailing list