[Pacemaker] [Problem] The "dampen" parameter of the attrd_updater command is ignored, and an attribute is updated.

[renayama19661014 at ybb.ne.jp]

Hi All,

The attrd_updater command ignores the "dampen" parameter and updates an attribute.

Step1) Start one node.
[root at srv01 ~]# crm_mon -1 -Af
Last updated: Tue May 27 19:36:35 2014
Last change: Tue May 27 19:34:59 2014
Stack: corosync
Current DC: srv01 (3232238180) - partition WITHOUT quorum
Version: 1.1.11-f0f09b8
1 Nodes configured
0 Resources configured


Online: [ srv01 ]


Node Attributes:
* Node srv01:

Migration summary:
* Node srv01: 

Step2) Update an attribute by attrd_updater command.
[root at srv01 ~]# attrd_updater -n default_ping_set -U 500 -d 3000       

Step3) The attribute is updated without waiting for the time of the "dampen" parameter.
[root at srv01 ~]# cibadmin -Q | grep ping_set            
          <nvpair id="status-3232238180-default_ping_set" name="default_ping_set" value="500"/>

The next code seems to have a problem somehow or other.

--- attrd/command.c -----
(snip)
    /* this only involves cluster nodes. */
    if(v->nodeid == 0 && (v->is_remote == FALSE)) {
        if(crm_element_value_int(xml, F_ATTRD_HOST_ID, (int*)&v->nodeid) == 0) {
            /* Create the name/id association */
            crm_node_t *peer = crm_get_peer(v->nodeid, host);
            crm_trace("We know %s's node id now: %s", peer->uname, peer->uuid);
            if(election_state(writer) == election_won) {
                write_attributes(FALSE, TRUE);
                return;
            }
        }
    }

Best Regards,
Hideo Yamauchi.