Hi, My setup is a 2 node cluster with 2 cloned resources. One is a IPaddr2 resource that is managing a IP with CLUSTERIP. Meaning that when both nodes are up each node runs 1 clone of this resouce and in case one of the 2 nodes is down the other node should run the 2 clones so that CLUSTERIP is configured to accept all traffic. The second resource is the actual daemon of the service running on the node. This is also a cloned resource but configured that there are max 2 clones and each node runs max 1 node.
The problem is that I can't move the IPaddr2 resource between nodes using the crm_resource command. This is the command I run : crm_resource -M -r resource_ip200:1 -N slave1 -VV And this is the log output related to the command : Dec 10 14:18:09 slave1 crm_resource: [3370]: info: Invoked: crm_resource -M -r resource_ip200:1 -N slave1.brussels.ns.dns.be -VV Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: Deleting <rsc_location id="cli-prefer-resource_ip200:1" /> Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update <constraints > Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update <rsc_location id="cli-prefer-resource_ip200:1" rsc="resource_ip200:1" > Dec 10 14:18:09 slave1 cib: [3075]: info: cib_process_request: Operation complete: op cib_delete for section constraints (origin=local/crm_resource/3): ok (rc=0) Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update <rule id="cli-prefer-rule-resource_ip200:1" score="INFINITY" boolean-op="and" > Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update <expression id="cli-prefer-expr-resource_ip200:1" attribute="#uname" operation="eq" value=" slave1.brussels.ns.dns.be" type="string" /> Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update </rule> Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update </rsc_location> Dec 10 14:18:09 slave1 crm_resource: [3370]: notice: log_data_element: migrate_resource: CLI Update </constraints> Dec 10 14:18:09 slave1 cib: [3075]: ERROR: Type IDREF doesn't allow value 'resource_ip200:1' Dec 10 14:18:09 slave1 cib: [3075]: ERROR: Element rsc_location failed to validate attributes Dec 10 14:18:09 slave1 cib: [3075]: ERROR: Type ID doesn't allow value 'cli-prefer-rule-resource_ip200:1' Dec 10 14:18:09 slave1 cib: [3075]: ERROR: Element rule failed to validate content Dec 10 14:18:09 slave1 crm_resource: [3370]: WARN: cib_native_perform_op: Call failed: Update does not conform to the configured schema/DTD Dec 10 14:18:09 slave1 cib: [3075]: ERROR: Element rsc_location failed to validate content Dec 10 14:18:09 slave1 crm_resource: [3370]: WARN: main: Error performing operation: Update does not conform to the configured schema/DTD Dec 10 14:18:09 slave1 cib: [3075]: ERROR: Element cib failed to validate content Dec 10 14:18:09 slave1 cib: [3075]: WARN: cib_perform_op: Updated CIB does not validate against pacemaker-1.0 schema/dtd It looks like the Pacemaker 1.0 syntax can't handle the ":" character as a ID. But this conflicts on how it names clone resources. Do I read this correct ? Thanks, Tim -- Tim Verhoeven - [EMAIL PROTECTED] - 0479 / 88 11 83 Hoping the problem magically goes away by ignoring it is the "microsoft approach to programming" and should never be allowed. (Linus Torvalds) _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
