Re: "crm node show" = "node-01(1): normal"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jul 6, 2012 at 2:42 AM, Gregory Bartholomew
<gregory.lee.bartholomew@xxxxxxxxx> wrote:
> Hi,
>
> I'm getting:
>
> WARNING: 2: ldap-ip-on-node-01: referenced node node-01 does not exist
>
> when I run:
>
> cat <<- "END" | crm
> configure primitive ldap-ip ocf:heartbeat:IPaddr2 params ip="x.x.x.x"
> cidr_netmask="32" op monitor interval="30s"
> configure location ldap-ip-on-node-01 ldap-ip inf: node-01

Looks like the shell assumes that node-01 should be the node's 'id'
(which is actually 1) instead of its uname.

> END
>
> "uname -n" shows:
>
> [root@node-01 ~]# uname -n
> node-01
>
> but "crm node show" shows:
>
> [root@node-01 ~]# crm node show
> node-01(1): normal
>
> cibadmin --query | grep "node-01" shows:
>
> [root@node-01 ~]# cibadmin --query | grep "node-01"
> <cib epoch="9" num_updates="16" admin_epoch="14"
> validate-with="pacemaker-1.2" cib-last-written="Thu Jul  5 11:23:19 2012"
> crm_feature_set="3.0.6" update-origin="node-01" update-client="cibadmin"
> have-quorum="1" dc-uuid="1">
>       <node id="1" type="normal" uname="node-01"/>
>       <rsc_location id="ldap-ip-on-node-01" node="node-01" rsc="ldap-ip"
> score="INFINITY"/>
>     <node_state id="1" uname="node-01" ha="active" in_ccm="true"
> crmd="online" join="member" expected="member"
> crm-debug-origin="do_update_resource" shutdown="0">
>
> Using the string "node-01(1)" that was output from the "crm node show"
> command does not seem to help either:
>
> [root@node-01 ~]# cat <<- "END" | crm
>> configure primitive nfs-ip ocf:heartbeat:IPaddr2 params
>> ip="146.163.150.231" cidr_netmask="32" op monitor interval="30s"
>> configure location nfs-ip-on-node-01 nfs-ip inf: node-01(1)
>> END
> WARNING: 2: nfs-ip-on-node-01: referenced node node-01(1) does not exist
> [root@node-01 ~]#
>
> I'm thinking that I have managed to create a situation where the node's name
> is inconsistently stored the configuration.  Can someone here confirm that
> this is or isn't the problem or otherwise help me to resolve this issue.
>
> Thanks,
> gb
>
> _______________________________________________
> discuss mailing list
> discuss@xxxxxxxxxxxx
> http://lists.corosync.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss


[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux