I have 5 servers in a cluster. Previously, to maintain the servers, I configured pvecm expected 1 and migrated the vms, thus being able to update the servers individually. Now, I can't repeat this process because when I restart a server the others automatically restart bringing down the entire cluster. I saw in other topics that it is due to a change in corosync, but the question remains: does this change make sense?. Because if the cluster is about availability, it does not make sense to impose this because it ends up taking down all services in a simple restart of just one server.
pve-manager/6.4-6/be2fa32c (running kernel: 5.4.114-1-pve)
pvecm status
Cluster information
-------------------
Name: Cluster0
Config Version: 5
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Wed Jul 7 12:06:14 2021
Quorum provider: corosync_votequorum
Nodes: 5
Node ID: 0x00000001
Ring ID: 1.1b0c
Quorate: Yes
Votequorum information
----------------------
Expected votes: 5
Highest expected: 5
Total votes: 5
Quorum: 3
Flags: Quorate
I try to set to 3:
pvecm expected 3
Unable to set expected votes: CS_ERR_INVALID_PARAM.
pve-manager/6.4-6/be2fa32c (running kernel: 5.4.114-1-pve)
pvecm status
Cluster information
-------------------
Name: Cluster0
Config Version: 5
Transport: knet
Secure auth: on
Quorum information
------------------
Date: Wed Jul 7 12:06:14 2021
Quorum provider: corosync_votequorum
Nodes: 5
Node ID: 0x00000001
Ring ID: 1.1b0c
Quorate: Yes
Votequorum information
----------------------
Expected votes: 5
Highest expected: 5
Total votes: 5
Quorum: 3
Flags: Quorate
I try to set to 3:
pvecm expected 3
Unable to set expected votes: CS_ERR_INVALID_PARAM.