[ClusterLabs] Updated attribute is not displayed in crm_mon
井上 和徳
inouekazu at intellilink.co.jp
Wed Aug 2 05:59:57 EDT 2017
Hi,
In Pacemaker-1.1.17, the attribute updated while starting pacemaker is not displayed in crm_mon.
In Pacemaker-1.1.16, it is displayed and results are different.
https://github.com/ClusterLabs/pacemaker/commit/fe44f400a3116a158ab331a92a49a4ad8937170d
This commit is the cause, but the following result (3.) is expected behavior?
[test case]
1. Start pacemaker on two nodes at the same time and update the attribute during startup.
In this case, the attribute is displayed in crm_mon.
[root at node1 ~]# ssh -f node1 'systemctl start pacemaker ; attrd_updater -n KEY -U V-1' ; \
ssh -f node3 'systemctl start pacemaker ; attrd_updater -n KEY -U V-3'
[root at node1 ~]# crm_mon -QA1
Stack: corosync
Current DC: node3 (version 1.1.17-1.el7-b36b869) - partition with quorum
2 nodes configured
0 resources configured
Online: [ node1 node3 ]
No active resources
Node Attributes:
* Node node1:
+ KEY : V-1
* Node node3:
+ KEY : V-3
2. Restart pacemaker on node1, and update the attribute during startup.
[root at node1 ~]# systemctl stop pacemaker
[root at node1 ~]# systemctl start pacemaker ; attrd_updater -n KEY -U V-10
3. The attribute is registered in attrd but it is not registered in CIB,
so the updated attribute is not displayed in crm_mon.
[root at node1 ~]# attrd_updater -Q -n KEY -A
name="KEY" host="node3" value="V-3"
name="KEY" host="node1" value="V-10"
[root at node1 ~]# crm_mon -QA1
Stack: corosync
Current DC: node3 (version 1.1.17-1.el7-b36b869) - partition with quorum
2 nodes configured
0 resources configured
Online: [ node1 node3 ]
No active resources
Node Attributes:
* Node node1:
* Node node3:
+ KEY : V-3
Best Regards
More information about the Users
mailing list