Increasing node votes in a cluster

[abale.ls]

I have a cluster with 2 nodes, and as configured by default, they both have 1 vote and will not reach quorum:

Votequorum information
----------------------
Expected votes:   2
Highest expected: 2
Total votes:      1
Quorum:           2 Activity blocked
Flags:

I've tried stopping the pve-cluster service and coreosync, editing the corosync.conf file in /etc/corosync (on both machines) to increase the votes of the primary nodes to 2 and increment the configversion, but it seems that after starting both corosync and pve-cluster, the file will be back to the old config with 1 vote.

If somebody can point me in the right direction (or tell me if 2 node cluster is not supported) then I would appreciate it!

nodelist {
  node {
    name: hv02
    nodeid: 2
    quorum_votes: 1
    ring0_addr: hv02
  }

  node {
    name: hv01
    nodeid: 1
    quorum_votes: 1
    ring0_addr: hv01
  }

}

quorum {
  provider: corosync_votequorum
}

 

[dietmar]

I have a cluster with 2 nodes, and as configured by default, they both have 1 vote and will not reach quorum:

Why don't the reach quorum?

 

[abale.ls]

Why don't the reach quorum?

Quorum:           2 Activity blocked

Is this a normal state? I was under the impression it could not reach quorum (both nodes only see themselves in the pvecm status)

 

[dietmar]

You have:

Total votes: 1

So only one node seems to be online (or multicast is not working).

 

[abale.ls]

If I reset the cluster and re-add them, they can see eachother until a reboot, at which point they can no longer see one-another.

 

[abale.ls]

multicast seems to be working:

from first node:

# omping stl2hv01 stl2hv02
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : waiting for response msg
stl2hv01 : joined (S,G) = (*, 232.43.211.234), pinging
stl2hv01 :   unicast, seq=1, size=69 bytes, dist=0, time=0.261ms
stl2hv01 : multicast, seq=1, size=69 bytes, dist=0, time=0.311ms
stl2hv01 :   unicast, seq=2, size=69 bytes, dist=0, time=0.349ms
stl2hv01 : multicast, seq=2, size=69 bytes, dist=0, time=0.375ms
stl2hv01 :   unicast, seq=3, size=69 bytes, dist=0, time=0.356ms

from second node:

# omping stl2hv01 stl2hv02
stl2hv02 : waiting for response msg
stl2hv02 : joined (S,G) = (*, 232.43.211.234), pinging
stl2hv02 :   unicast, seq=1, size=69 bytes, dist=0, time=0.384ms
stl2hv02 :   unicast, seq=2, size=69 bytes, dist=0, time=0.345ms
stl2hv02 : multicast, seq=2, size=69 bytes, dist=0, time=0.439ms

 

[abale.ls]

I just caught this actually, from the second node - not sure fi related (crm and lrm both throw this)

Oct 19 13:20:09 stl2hv02 pve-ha-crm[2421]: ipcc_send_rec failed: Connection refused
Oct 19 13:20:09 stl2hv02 pve-ha-crm[2421]: ipcc_send_rec failed: Connection refused