Search results

I rebooted the two hosts I wanted to migrate between and now everything works again.

I tried some of the above post without rebooting hosts; # pvecm updatecert -f # systemctl restart pvedaemon pveproxy pve-cluster No change. No idea how to get past this after a full day of reading so far. The doc says if you unattach a node, you can run pvecm updatecerts to update its certs...

Without changing anything in the certs files, I ran the following; pvecm updatecert -f systemctl stop pve-cluster systemctl start pve-cluster No change. I've been reading the link you gave me but it's hard to know what to do/try without taking chances of breaking something. I don't have...

On host 01, I see multiple keys for the same hosts in /etc/pve/priv/authorized_keys but in /etc/pve/priv/known_hosts, only one of each. Same on all of the hosts in the cluster. Is it safe to remove the multiples in the first file and will that solve the issue?

I re-ran the command on just one host and still seeing the same. Now I'm getting a certificate failed when clicking on any other node than the one I'm logged into (GUI). The cli command shows the cluster is up and running with quorum so really not sure what to do now.

Sorry, I updated my previous comment several times. Cluster seems fine, from the command line.

Hi, Thanks for your reply. I'm kind of stuck until I solve this :). I ran this on every host. Then I tried to migrate again and got this; Then, logged into the first host, I clicked on another host and got this; So now it seems it's even more broken.

Solved: https://forum.proxmox.com/posts/606419/ Some time back, I upgraded my hosts to 8.0.3 and all seemed to be fine. All of sudden, I'm not able to migrate a host and keep getting the ssh key warning. I logged into both hosts that I wanted to migrate between and tried to ssh from one to the...

For me, it was a lot simpler to just migrate vms to another host, upgrade one host at a time moving vms back once done. Simple, clean, no old files left behind.

I wasn't sure if changing the password on the host one other host connected to join the cluster would break that. Thank you, I'll change the passwords then.

When I started playing with proxmox, I set very simple passwords on the hosts I set up. I then joined them in a cluster using the same bad password across all hosts. Now that I'm being a little more serious with this, I'd like to have better passwords but am not sure how to go about it. Do I...

Understood. Never had to use dracut for anything newer than 7.9 so I assume this is for older versions only. Either way, it worked perfectly thanks to this thread so thank you.

I notice the latest release is 8.0.2. Does this mean if I upgrade now, there will be many more updates to have to upgrade which would be very disruptive. It seems like waiting would be more prudent?

Is it possible to install one v8 and bring it into a cluster than is all 7.3? This way, I could migrate vms away from the 7.3 hosts to upgrade those as well.

Sure but that doesn't answer my question. If the import doesn't work and you have to keep it on esx for a while longer, will it still start/run ok on esx after running the commands? Obviously, backing up or snapshot before making the change is the best idea but some might not remember to do that.

I know this is old but I'm still struggling with this also. Are you saying to run this before importing to proxmox? If this is done and the vm doesn't completely run on proxmox, does it make it broken on vmware?

Thank you . Funny that I had not found that.

I guess the answer is no.

Is there any chance that the console allows or will eventually allow cut/paste? There so so many situations where I have to enter huge long complicated passwords to get in via the console and pasting would be so much more efficient.

Can a mod delete this please.