Update from 8.0 to 8.2

[Clericer]

Hey everyone,

I have a cluster running Proxmox 8.0.3 and I need to add a new node. However, I'm encountering certificate errors and other compatibility issues when trying to add a server with version 8.2.

I couldn't find version 8.0 in the Proxmox download archives to install the new server on the same version.

What is the correct procedure to upgrade from 8.0 to 8.2? Should I:

1. Shutdown all VMs,
2. Leave the cluster,
3. Update via the web UI (or is the CLI preferred)?

Is it better to upgrade from 8.0 to 8.1 first, and then to 8.2? When I search for Proxmox upgrades in forums or on Google, I see many reports of corrupted or non-functional systems, which I want to avoid.

Do I need an Enterprise subscription for a smooth upgrade process? I don’t have one on all cluster nodes.

I appreciate any information.

 

[Moayad]

Hi,

Could you please post the error you get when you try to add a new node to your cluster?

Is it better to upgrade from 8.0 to 8.1 first, and then to 8.2?

The upgrade from 8.0 to the Proxmox VE 8.2.x should be done in one step using `apt update && apt dist-upgrade` [0].

Do I need an Enterprise subscription for a smooth upgrade process? I don’t have one on all cluster nodes.

No.



[0] https://forum.proxmox.com/threads/proxmox-ve-8-2-released.145722/

 

[andreisrr]

I am trying to make an upgrade (ie not reinstalling from scratch) PVE-8.1.3 to PVE-8.2.x.
I don't have an enterprise subscription and according to previous answer I don't need one.

Running apt update && apt dist-upgrade fails because the apt update finishes with exitcode 100.

I get these errors:

E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-quincy/dists/bookworm/InRelease  401  Unauthorized [IP: 185.219.221.167 443]
E: The repository 'https://enterprise.proxmox.com/debian/ceph-quincy bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/bookworm/InRelease  401  Unauthorized [IP: 185.219.221.167 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve bookworm InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

I don't use Ceph, so the first one wouldn't be a problem, however, by my reading, the second one would be.

Manually running separately apt update and then apt dist-upgrade will result in some packages being upgraded, but after a host reboot, it still says in the top bar: Proxmox Virtual Environment 8.1.3

Please, how can I do the upgrade to PVE-8.2.x?

 

[sw-omit]

Since you don't have an enterprise subscription, you don't have access to the enterprise repository, which you are trying to access and as such it errors out.
From the gui, go to the server -> Update -> Repository, and there click the Proxmox enterprise repo, then click disable so you no longer try to access that repo.
Then next to that click add, select the "Proxmox no-subscription" repository.
Finally, either run the commands or go up a tab in the GUI to the "update" tab, click refresh, then click update, press Y to confirm (after checking that nothing is wrong/strange in what it is going to install) and you're good.
Once the update is done, because it is a large upgrade, make sure to reboot the server afterwards

EDIT: Also, regarding your other questions, no, you can just upgrade in place, like 99% of all updates of systems. Since you do need a reboot, you will have to shutdown your VM's or move them to a different server in the cluster, but you don't have to (or better said, you should NOT) leave the cluster

EDIT 2: Since you say you don't have a subscription on all the nodes, do you mean that some do and some don't have a subscription? If so, two things to note:
1. If those licenses are above the "community" edition, they would normally entitle you to support-tickets directly to proxmox, but if I recall correctly, this is only the case if all servers in a cluster have the same subscription-level.
2. It is generally advised to have all servers in a cluster running at the same update-version, except while you're upgrading of course, but since you're getting from different repo's, that will be tricky.

 

[andreisrr]

Thank you.
Solved it. Also with some help in this thread: https://forum.proxmox.com/threads/vm-migration-failed-host-key-verification-failed.154179/