Error in promote a join cluster

[Pedro Lagonell]

Hi, when I try to promote a cluster, it gives an error:
Establishing API connection with host 'x.x.x.x'
Login succeeded.
Request addition of this node
TASK ERROR: 400 Parameter verification failed. link0: property is not defined in schema and the schema does not allow additional properties

 

[Stoiko Ivanov]

Make sure all nodes have the same version of PVE installed - this message seems like either one of your nodes is lagging behind, or you're trying to join a PVE 6.0 node to a not fully up to date PVE 5.4 cluster.

check the output of `pveversion -v`

 

[jangardian]

Hello, I have same problem. Trying to add node with PVE 6.0 to cluster with PVE 5.0. After this I plan to migrate servers to this new node and upgrade all PVE 5.0 nodes to version 6.0. But during joining cluster from node with PVE 6.0 I get bellow error:
"
An error occured on the cluster node: Parameter verification failed.
! property is not defined in schema and the schema does not allow additional properties
TASK ERROR: Cluster join aborted!
"
All nodes in cluster with PVE 5.0 have proxmox-ve: 5.4-2 (running kernel: 4.15.18-29-pve), pve-manager: 5.4-15 (running version: 5.4-15/d0ec33c6) with latest updates possible.
PVE 6.0 node have proxmox-ve: 6.2-1 (running kernel: 5.4.41-1-pve), pve-manager: 6.2-4 (running version: 6.2-4/9824574a)

Also I already updated corosync at PVE 5.0 nodes to version corosync: 3.0.3-pve1~bpo9.

Thank you for any good hint.

 

[t.lamprecht]

Trying to add node with PVE 6.0 to cluster with PVE 5.0.

This is not supported, either join a new node with 5.4 and then upgrade or upgrade and then join.

 

[TheMrg]

we create cluster on nodeA with VE 5.4-10
we create new nodeB with VE 6.3-3
we get:
! property is not defined in schema and the schema does not allow additional properties
TASK ERROR: Cluster join aborted!

Is there no way? we like to create a cluster because we want easy migrate vms to nodeB to upgrade nodeA. We can not upgrade nodeA with running productive VMs on it.

 

[t.lamprecht]

Is there no way? we like to create a cluster because we want easy migrate vms to nodeB to upgrade nodeA. We can not upgrade nodeA with running productive VMs on it.

As said:

This is not supported, either join a new node with 5.4 and then upgrade or upgrade and then join.

So, create node B also with 5.4, join, then upgrade, then migrate VMs then upgrade node A.

PVE 5.4 ISO: http://download.proxmox.com/iso/

Upgrade documentation: https://pve.proxmox.com/wiki/Upgrade_from_5.x_to_6.0

 

[TheMrg]

thanks, we not try a way with pve-zsync
it is a great tool, so we can lower the downtime