vm info keeps loading in VE 7.0.11

[amey]

Hello,

I have an existing proxmox VE cluster on 6.3.2 version

I have added a new physical server in the existing proxmox cluster
The new server has Proxmox VE 7.0.11 version.

Problem is, when I click on any vm which is on VE 7.0.11, the info keeps loading with the circle.
I tried rebooting the physical server but same issue.
If I double click on the vm, it shows the graphical UI in a new window without any issue.

PFA containing the image for reference.
Is it due to compatibility issue?

Thanks & Regards,
Amey.

 

[Moayad]

Hi,

I guess you should renew the cluster certificate `pvecm updatecerts -f`

 

[amey]

Hi,

I guess you should renew the cluster certificate `pvecm updatecerts -f`

I should execute this command on the newly added proxmox server? Thanks.

 

[amey]

I just tried to execute the command on the newly added server.
Same issue continues.

root@prod-proxmox-svr3:~# pvecm updatecerts --force
(re)generate node files
generate new node certificate
merge authorized SSH keys and known hosts

 

[amey]

Quick update:

After logout & login back in cluster via web UI, I am getting following error when I click on any vm on newly added server =

tls_process_server_certificate: certificate verify failed (596)

 

[Moayad]

Is there anything in the Syslog/journal of the cluster node?
Have you tried browsing the node in another browser?

In general: the mixing of the PVE version is not recommended, may I ask you why you want to use PVE 6 with PVE 7?

 

[amey]

Is there anything in the Syslog/journal of the cluster node?
Have you tried browsing the node in another browser?

In general: the mixing of the PVE version is not recommended, may I ask you why you want to use PVE 6 with PVE 7?

I found something interesting after referring to similar threads =

I have following entry of same IP in proxmox servers =

10.200.104.46 ssh-rsa AAAAB3NzaCeIp9OuDOin+6yrTJ+ECo9KE0n0/pxUXIYpmkak=
prod-proxmox-svr3 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC9G/Iye0CeEbH0RakjQuPKb0=
10.200.104.46 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC9G/Iye=

1st entry in the list is wrong 1.
I reinstalled proxmox on the same physical server due to subnet change.
If I manually remove the orphan ssh key entry from remaining servers, will that fix the issue?

Is there anything in the Syslog/journal of the cluster node?

No. Just normal logs.

Have you tried browsing the node in another browser?

Yes. Same issue.

In general: the mixing of the PVE version is not recommended, may I ask you why you want to use PVE 6 with PVE 7?

I am relatively new to Proxmox.
I did not check compatibility matrix before adding this 7.x server in 6.x cluster.

 

[Moayad]

Hi,

10.200.104.46 ssh-rsa AAAAB3NzaCeIp9OuDOin+6yrTJ+ECo9KE0n0/pxUXIYpmkak= prod-proxmox-svr3 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC9G/Iye0CeEbH0RakjQuPKb0= 10.200.104.46 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQC9G/Iye=

The pvecm updatecerts -f command will add the nodes fingerprint to the /etc/pve/priv/known_hosts file which is shared across the cluster. For each node the file /etc/ssh/ssh_known_hosts should be a symlink to the /etc/pve/priv/known_hosts file.

Try to ssh to the new node from one of your nodes if you get a message that the key has changed, you should use the ssh-keygen -f command to delete it or you can do that manually (get rid of the duplicate entry in the "ssh_known_hosts").

Then do the `pvecm updatecerts -f` on the affected nodes.

I did not check compatibility matrix before adding this 7.x server in 6.x cluster.

You could upgrade the PVE 6 to PVE 7 by following our wiki guide [0]