Adding a new node changes corosync token timeout

Issue

• After adding new corosync nodes, the runtime totem.token for pacemaker cluster gets increased.

• It is expected to be the token value as defined in totem {} directive of corosync configuration file /etc/corosync/corosync.conf:

[root@node2 ~]# cat /etc/corosync/corosync.conf
totem {
    version: 2
    cluster_name: mycluster
    secauth: off
    transport: udpu
    token: 5000
}

However, the 'runtime.config.totem.token' value of from corosync-cmapctl doesn't seem to related to 'totem.token' specified in the corosync configuration:

[root@node2 ~]# corosync-cmapctl | grep totem.token
runtime.config.totem.token (u32) = 5650
totem.token (u32) = 5000