Hi,
On Wed, 23 Jan 2013 18:52:20 +0100
Dejan Muhamedagic <deja...@fastmail.fm> wrote:
> > <nodes>
> > <node id="35956928" uname="sipc2n2">
>
> Note sure if id can start with a digit.
Corosync node id's are always digits-only.
> This should really work with versions >= v1.2.4
Yeah… I have looked into the crmsh code and it has explicit support for
node 'type' attribute in Pacemaker 1.1.8. For some reason this does not
work for me on this cluster (no such problems on another cluster, which
was not upgraded, but set up on Pacemaker 1.1 from the beginning).
> Which schema do you validate against? Look for the validate-with
> attribute of the cib element.
validate-with="pacemaker-1.0"
<element name="node">
<attribute name="id"><text/></attribute>
<attribute name="uname"><text/></attribute>
<attribute name="type">
<choice>
<value>normal</value>
<value>member</value>
<value>ping</value>
</choice>
</attribute>
So no, it is not optional here. But it is optional in the pacemaker-1.1 schema.
So the problem is crmsh uses the wrong schema for the XML it generates…
# cibadmin -Q | grep validate-with
<cib validate-with="pacemaker-1.0" crm_feature_set="3.0.6" have-quorum="1"
admin_epoch="0" epoch="337" num_updates="158" cib-last-written="Wed Jan 23
15:23:22 2013" dc-uuid="19179712">
So, the 'validate-with="pacemaker-1.0"' comes from the current CIB. crmsh keeps
that, but generates Pacemaker 1.1 XML, so the verification fails.
I should probably upgrade my CIB somehow, but still it seems there is a bug in
crmsh.
Greets,
Jacek
_______________________________________________
Pacemaker mailing list: Pacemaker@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
