[ClusterLabs] Node attribute disappears when pacemaker is started

井上 和徳 inouekazu at intellilink.co.jp
Wed May 24 12:13:22 CEST 2017


Hi,

After loading the node attribute, when I start pacemaker of that node, the attribute disappears.

1. Start pacemaker on node1.
2. Load configure containing node attribute of node2.
   (I use multicast addresses in corosync, so did not set "nodelist {nodeid: }" in corosync.conf.)
3. Start pacemaker on node2, the node attribute that should have been load disappears.
   Is this specifications ?

1.
[root at rhel73-1 ~]# systemctl start corosync;systemctl start pacemaker
[root at rhel73-1 ~]# crm configure show
node 3232261507: rhel73-1
property cib-bootstrap-options: \
  have-watchdog=false \
  dc-version=1.1.17-0.1.rc2.el7-524251c \
  cluster-infrastructure=corosync

2.
[root at rhel73-1 ~]# cat rhel73-2.crm
node rhel73-2 \
  utilization capacity="2" \
  attributes attrname="attr2"

[root at rhel73-1 ~]# crm configure load update rhel73-2.crm
[root at rhel73-1 ~]# crm configure show
node 3232261507: rhel73-1
node rhel73-2 \
  utilization capacity=2 \
  attributes attrname=attr2
property cib-bootstrap-options: \
  have-watchdog=false \
  dc-version=1.1.17-0.1.rc2.el7-524251c \
  cluster-infrastructure=corosync

3.
[root at rhel73-1 ~]# ssh rhel73-2 'systemctl start corosync;systemctl start pacemaker'
[root at rhel73-1 ~]# crm configure show
node 3232261507: rhel73-1
node 3232261508: rhel73-2
property cib-bootstrap-options: \
  have-watchdog=false \
  dc-version=1.1.17-0.1.rc2.el7-524251c \
  cluster-infrastructure=corosync

Regards,
Kazunori INOUE



More information about the Users mailing list