[Pacemaker] resource locations for cloned resources (asymmetric cluster)

Bernd Schubert bs_lists at aakef.fastmail.fm
Thu Aug 26 16:02:28 EDT 2010


Hi all,

I'm trying to start a pingd clone resource on an asymmetric cluster. 
I specified locations, but it still refuses to start pingd

===
[root at vrhel5-mds1 ha.d]# cat pingd.cib 
primitive pingdnet1 ocf:pacemaker:pingd                                                         
\
        params  host_list="10.0.2.17 10.0.2.18 10.0.2.19 10.0.2.20 10.0.2.21 
10.0.2.22"         \
        name=pingdnet1                                                                          
\
        op monitor timeout=120 interval=120                                                     
\
        op start   timeout=120                                                                  
\
        op stop    timeout=120

clone cl-pingdnet1 pingdnet1

location l-pingdnet1-mds1 cl-pingdnet1 100: mds1
location l-pingdnet1-mds2 cl-pingdnet1 100: mds2
location l-pingdnet1-oss1 cl-pingdnet1 100: oss1
location l-pingdnet1-oss2 cl-pingdnet1 100: oss2
location l-pingdnet1-oss3 cl-pingdnet1 100: oss3
location l-pingdnet1-oss4 cl-pingdnet1 100: oss4
===


After loading the file, it does not start pingd anywhere:

===
[root at vrhel5-mds1 ha.d]# hastatus
============
Last updated: Thu Aug 26 21:44:40 2010
Stack: Heartbeat
Current DC: vrhel5-oss4 (6071bbfc-0569-4a42-9430-b7ee1bb8457a) - partition 
with quorum
Version: 1.0.9-89bd754939df5150de7cd76835f98fe90851b677
6 Nodes configured, unknown expected votes
7 Resources configured.
============

Node vrhel5-mds2 (577fb716-0eab-4e28-988a-829e74291129): online
        st-ssh-vrhel5-mds1      (stonith:external/ssh) Started 
Node vrhel5-oss2 (09f4e5a9-eb4c-4be6-aa70-cfe377681e9a): online
        st-ssh-vrhel5-oss1      (stonith:external/ssh) Started 
Node vrhel5-oss3 (93ab053a-064c-4588-b938-829345a36254): online
        st-ssh-vrhel5-oss4      (stonith:external/ssh) Started 
Node vrhel5-oss4 (6071bbfc-0569-4a42-9430-b7ee1bb8457a): online
        st-ssh-vrhel5-oss3      (stonith:external/ssh) Started 
Node vrhel5-mds1 (182ee67f-bd1e-4b36-9d0d-87a3b72a2db5): online
        st-ssh-vrhel5-mds2      (stonith:external/ssh) Started 
Node vrhel5-oss1 (afa81e40-9959-489a-b020-7845373e1ff1): online
        st-ssh-vrhel5-oss2      (stonith:external/ssh) Started 

Inactive resources:

 Clone Set: cl-pingdnet1
     Stopped: [ pingdnet1:0 pingdnet1:1 pingdnet1:2 pingdnet1:3 pingdnet1:4 
pingdnet1:5 ]
===

Log file:

===
Aug 26 21:44:13 vrhel5-oss4 pengine: [5474]: info: native_color: Resource 
pingdnet1:0 cannot run anywhere
Aug 26 21:44:13 vrhel5-oss4 pengine: [5474]: info: native_color: Resource 
pingdnet1:1 cannot run anywhere
Aug 26 21:44:13 vrhel5-oss4 pengine: [5474]: info: native_color: Resource 
pingdnet1:2 cannot run anywhere
Aug 26 21:44:13 vrhel5-oss4 pengine: [5474]: info: native_color: Resource 
pingdnet1:3 cannot run anywhere
Aug 26 21:44:13 vrhel5-oss4 pengine: [5474]: info: native_color: Resource 
pingdnet1:4 cannot run anywhere
Aug 26 21:44:13 vrhel5-oss4 pengine: [5474]: info: native_color: Resource 
pingdnet1:5 cannot run anywhere
===


So it seams it does not accept the location string, but why? 
If I try to specify "pingdnet1:0" it fails either:

===
[root at vrhel5-mds1 ha.d]# crm configure location l-pingdnet1_0-mds1 pingdnet1:0 
inf: mds1
element rsc_location: Relax-NG validity error : Expecting an element rule, got 
nothing
element rsc_location: Relax-NG validity error : Element constraints has extra 
content: rsc_location
element configuration: Relax-NG validity error : Invalid sequence in 
interleave
element configuration: Relax-NG validity error : Element configuration failed 
to validate content
element cib: Relax-NG validity error : Element cib failed to validate content
crm_verify[21480]: 2010/08/26_21:05:15 ERROR: main: CIB did not pass 
DTD/schema validation
Errors found during check: config not valid
Do you still want to commit? Ctrl-C, leaving
===


Any help would be appreciated.


Thanks,
Bernd

-- 
Bernd Schubert
DataDirect Networks




More information about the Pacemaker mailing list