In case you want to rename the cluster name where you already have running hypervisors, you need ssh in every hypervisor do the following commands:
sqlite3 /var/lib/pve-cluster/config.db “SELECT * FROM tree WHERE name = ‘corosync.conf’;”
output —-
debug: off
to_syslog: yes
}nodelist {
node {
name: pve1
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.12.104
}
node {
name: pve2
nodeid: 2
quorum_votes: 1
ring0_addr: 192.168.12.109
}
}quorum {
provider: corosync_votequorum
}totem {
cluster_name: testms
config_version: 2
interface {
linknumber: 0
}
ip_version: ipv4-6
link_mode: passive
secauth: on
version: 2
}
Update command, that will replace the clustername, change your variables;
sqlite3 /var/lib/pve-cluster/config.db “UPDATE tree SET data = REPLACE(data, ‘cluster_name: originalclustername’, ‘cluster_name: newclustername’) WHERE name = ‘corosync.conf’;”
systemctl stop pvestatd.service pvedaemon.service pve-cluster.service corosync pve-cluster
systemctl start pvestatd.service pvedaemon.service pve-cluster.service corosync pve-cluster
Enjoy!