[Pacemaker] Some errors after upgrading from heartbeat 2.1 cluster

David Vossel dvossel at redhat.com
Mon Jul 23 14:17:08 EDT 2012


----- Original Message -----
> From: "Drew Morone" <andrewmorone at yahoo.com>
> To: pacemaker at oss.clusterlabs.org
> Sent: Monday, July 23, 2012 10:51:23 AM
> Subject: [Pacemaker] Some errors after upgrading from heartbeat 2.1 cluster
> 
> 
> 
> 
> Hi,
> I'm new to this list and have been searching for a solution for a few
> weeks to a problem I'm having, but not seeing anything similar to
> what i'm seeing.
> 
> 
> We have a 2 node active/standby cluster with the following services:
> drbd
> nfs
> dhcpd
> 
> 
> We currently upgraded our OS from Debian Lenny, to Squeeze, which in
> turn upgraded heartbeat to hearbeat(3.0.3) /pacemaker(1.0.9) . The
> upgrade actually went pretty well following this example:
> http://www.linux-ha.org/doc/users-guide/_upgrading_from_crm_enabled_heartbeat_2_1_clusters.html
> 
> and everything seems to work well, no down time, no loss of data. My
> only issue is that I'm getting some errors with some of the resource
> attributes and parameters, eg running 'crm configure verify' I'll
> get stuff like this:
> 
> ERROR: DRBD_data: attribute target_role does not exist
> ERROR: DRBD_data: parameter target_role does not exist
> 
> 
> 
> Here's the section of the converted schema it's complaining about:
> <primitive id="DRBD_data" class="heartbeat" type="drbddisk">
> <meta_attributes id="primitive-DRBD_data.meta">
> <nvpair id="nvpair.meta.auto-19" name="target_role" value="started"/>

I believe the meta attribute is target-role not target_role.

-- Vossel

> </meta_attributes>
> <instance_attributes id="instance_attributes.id179586">
> <nvpair id="nvpair.id178988" name="target_role" value="started"/>
> <nvpair name="target_role" value="drbd0" id="nvpair.id178172"/>
> </instance_attributes>
> </primitive>
> 
> 
> I'm assuming that those parameters are no longer used, or used
> differently in the heartbeat/pacemaker configurations. We upgraded
> to the new schema format. I don't want to rebuild the configuration
> from scratch, but I'm thinking maybe I might have to. Unless these
> errors are benign. Everything seems to work properly.
> 
> 
> Drew
> _______________________________________________
> 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://bugs.clusterlabs.org
> 




More information about the Pacemaker mailing list