Comment 10 for bug 1528488

Interesting, but restarting the corosync with pacemaker changes nothing as well. Even though the nodelist config in the corosync.conf looks correct:

nodelist {
  node {
    # node-5.test.domain.local
    ring0_addr: 10.109.2.6
    nodeid: 5
  }
  node {
    # node-4.test.domain.local
    ring0_addr: 10.109.2.4
    nodeid: 4
  }
  node {
    # node-6.test.domain.local
    ring0_addr: 10.109.2.9
    nodeid: 6
  }
  node {
    # node-2.test.domain.local
    ring0_addr: 10.109.2.8
    nodeid: 2
  }
}

I'm not sure if this is pure LCM case, as Slava described in the comment # 5 or the dynamic cluster scale issue as well