[SOLVED] Migration 5.4-15 to 6 : issue whit cluster configuration

[metaenlace]

Hello, it's time to migrate but i've that warn from pve5to6:

= CHECKING CLUSTER HEALTH/SETTINGS =

PASS: systemd unit 'pve-cluster.service' is in state 'active'
PASS: systemd unit 'corosync.service' is in state 'active'
PASS: Cluster Filesystem is quorate.

Analzying quorum settings and state..
INFO: configured votes - nodes: 1
INFO: configured votes - qdevice: 0
INFO: current expected votes: 1
INFO: current total votes: 1
WARN: cluster consists of less than three nodes!


I dont use cluster, i only have a server but i played around whit the gui when i installed the server three years ago and cluster "came up"

it's posible to remove the cluster configuration without losing data? if not, is there a problem updating the system?

thanks in advance

 

[t.lamprecht]

Hi,

As Proxmox VE 6 is already EOL I'd say the time to migrate started quite a while ago

it's posible to remove the cluster configuration without losing data? if not, is there a problem updating the system?

It is possible, but I don't think it's the best idea to do now, i.e. might be a bit invasive and it's not required if it's just one node "cluster"; the check maybe could special-case the situation were there's only one node configured in a cluster.

So, better to ignore the warning, at least if you really never joined any other node to this cluster.
If unsure, you could check if /etc/pve/corosync.conf contains only one node entry in the nodelist section.

 

[metaenlace]

only one node:

root@svrmetamvs1:/etc/pve# cat corosync.conf
logging {
debug: off
to_syslog: yes
}

nodelist {
node {
name: svrmetamvs1
nodeid: 1
quorum_votes: 1
ring0_addr: 192.168.1.220
}
}

quorum {
provider: corosync_votequorum
}

totem {
cluster_name: metaclusterprox
config_version: 1
interface {
bindnetaddr: 192.168.1.220
ringnumber: 0
}
ip_version: ipv4
secauth: on
version: 2
}

root@svrmetamvs1:/etc/pve#

then i suppose if i ignore de warning and upgrade i'll still have the cluster info, right?

 

[t.lamprecht]

then i suppose if i ignore de warning and upgrade i'll still have the cluster info, right?

Exactly, above is only mentioning one node and thus the warning can be ignored.

 

[metaenlace]

Exactly, above is only mentioning one node and thus the warning can be ignored.

Thanks.
I'll schedule the time then. Update snapshots, shutdown and backup virtual machines, verify backups, update proxmox and pray
I'll let you know how everything goes

 

[metaenlace]

Today was the day, i put all the vm's in other server and upgrade, first 5 to 6, then 6 to 7 and 7 to 8. All perfect, without any problem following the Proxmox official documentation.
It is very comforting to work with such good software.

 

[metaenlace]

[SOLVED]