[Pacemaker] crm shell and corosync2 node id
Dejan Muhamedagic
dejanmm at fastmail.fm
Thu Sep 13 14:37:39 CEST 2012
Hi,
On Thu, Sep 13, 2012 at 02:57:54PM +0300, Vladislav Bogdanov wrote:
> Hi Dejan, all,
>
> current crm shell (b58a3398bf11) can not parse node 'id' attribute when
> running on corosync 2:
>
> # crm configure show |grep xml
> INFO: object 1074005258 cannot be represented in the CLI notation
> INFO: object 1090782474 cannot be represented in the CLI notation
> INFO: object 1107559690 cannot be represented in the CLI notation
> INFO: object 1124336906 cannot be represented in the CLI notation
> xml <node id="1074005258" uname="vd01-a"> \
> xml <node id="1090782474" uname="vd01-b"> \
> xml <node id="1107559690" uname="vd01-c"> \
> xml <node id="1124336906" uname="vd01-d"> \
A quick test here shows that it can:
$ crm configure show 1074005258
node $id="1074005258" lmb-virt-01 \
attributes cores="2" \
utilization cores="2"
$ crm configure show xml 1074005258
...
<node id="1074005258" type="normal" uname="lmb-virt-01">
Hmm, I wonder if the type attribute missing is a problem here.
IIRC, it used to be a required attribute and it is so here in
v1.1.7. Looks like that changed in the meantime.
Thanks,
Dejan
>
> Best,
> Vladislav
>
> _______________________________________________
> 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