How can I upgrade PVE 8.2.2 to 8.2.4?

[yanminaung]

Hello All,

I have 4 nodes cluster with version 8.2.4 in my production.

I would like to add 2 more nodes (total 6 nodes). But what I can find is 8.2.2 ISO only.

So I installed 8.2.2 on 2 new nodes.

What I am thinking is before I join to the existing cluster I would like to upgrade those new nodes to the version 8.2.4 only to match with existing nodes.

Please kindly share whatever your idea for my case. Thanks.

PS: At the moment I cannot make any changes to existing 4 nodes which is running PVE 8.2.4.

 

[aj@root]

Yes, I highly recommend that all nodes be the same version, including Ceph (quincy, reef, squid), if you are using Ceph.

Due to the rolling release cycle (which is how almost Linux distros work), the only way to have a true snapshot of the release is either on the ISO or the dpkg list.

Commandline (Snapshot & Sync Versions)

Although not officially supported by Proxmox, Debian supports syncing versions between systems using `dpkg`.

On the 8.2.4 system:

# export list of package versions
dpkg-query -Wf '${Package}=${Version}\n' > ./proxmox-8.2.4-packages.txt

The file will look like this

procmail=3.22-27
procps=2:4.0.2-3
proxmox-archive-keyring=3.1
proxmox-backup-client=3.3.4-1
proxmox-grub=2.06-13+pmx6
proxmox-kernel-6.8=6.8.12-9
pve-cluster=8.0.10
pve-container=5.2.4
...

Copy that file over to the 8.2.2 system and run `apt install` with it:

# import list of package versions on the other system
apt install -y $(cat ./proxmox-8.2.4-packages.txt)

This is similar to running something like sudo apt install libpve-access-control=8.2.1, but with all of the packages and their exact version.

Commandline (Normal Dist Upgrade)

To bring each system up to the latest current version via CLI:

apt-get update
apt-get dist-upgrade

pveupdate
pveupgrade

To learn how to change update repositories from the command line, see: https://ryanburnette.com/blog/proxmox-updates/

Web UI (Normal Dist Upgrade)

To bring each system up to the latest current version via the Web UI:

Refresh the repository listings.

If you have an Enterprise subscription, disable the No-Subscription repository (if any).
If you do not have a paid subscription, disable the Enterprise repository.


Likewise, make sure that you do have either the Enterprise or No-Subscription repository added for both PVE and Ceph
(be sure to use the same Ceph version on all nodes, and only upgrade one version at a time - such as from Quincy to Reef)

Then refresh the package lists, and upgrade them.

 

[gfngfn256]

apt upgrade
apt distupgrade

Apart from leesteken justly comment of NEVER using apt upgrade on PVE, that second command should be apt dist-upgrade not distupgrade

It seems you missed the OP's question that actually concerns updating only to a specific version. leesteken has aptly responded to this (pun intended!).

 

[aaron]

Since Proxmox VE follows a rolling release model, there is no way to install a specific version. That term is also hard to define, because even if the GUI says you are on 8.2.4, some other packages could be on several possible versions.

Either update the other nodes as well, or, for the future, you could use the Proxmox Offline Mirror to create snapshots of the update repositories that you point your hosts to.

Thread 'Proxmox Offline Mirror released!'

Sep 15, 2022

We are proud to announce the first release of our new Proxmox Offline Mirror tool.

With the Proxmox Offline Mirror tool, you can manage a local apt mirror for all package updates for Proxmox and Debian projects. From this local apt mirror you can create an external medium, for example a USB flash drive or a local network share, to update systems which cannot access the package repositories directly (or proxied) via the internet. Such systems might be restricted by policies to access the public internet or are completely air-gapped. Finally, you can also manage subscriptions for such...

• t.lamprecht
• Replies: 180
• Forum: Proxmox VE: Installation and configuration

• 

 

[aj@root]

I was still doing research and updating the answer while y'all were responding and only just now got the updates.

Please advise in regards to the dpkg approach ^^.

Thanks for pointing out the dist-upgrade typo.

I wasn't aware of advice against using apt upgrade, I'll read that now.

 

[aj@root]

@gfngfn256 @leesteken I see apt upgrade also referenced in the Proxmox documentation here:
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_firmware_troubleshooting

Do you believe that that is a typo and should be apt dist-upgrade as well?

And is there any documentation as to why apt upgrade should be avoided?
(in my history with Linux I typically do that first out of habit, though I don't know why - it's just something I was taught and I haven't gone back to investigate it - I supposed I just assumed it was the "incremental" approach, which makes sense that it may not have any benefit for Proxmox)

 

[aj@root]

P.S. I see that my method of posting and editing caused some confusion and frustration. In the future I'll try to be more clear with something like "DRAFT: I responded early because I'm interested in answering this, please hold while I'm still researching and updating".

 

[aaron]

I see apt upgrade also referenced in the Proxmox documentation here:

Thanks, that must have slipped through. In the next version of the docs it will be aligned to avoid confusion
https://git.proxmox.com/?p=pve-docs.git;a=commitdiff;h=57cdb882248f08c2099751a5eb2d64669e26a9a2

 

[aj@root]

Thanks @aaron. Will you also throw in an explicit note to warn against apt upgrade and a short explanation?
I don't think its pitfalls are common knowledge and I'm fully on-board with following the recommendation, but after many years have having the "conventional wisdom" of doing the opposite, I believe it would help others aside from just myself to know.

Do you have any advice about apt-get dist-upgrade vs apt dist-upgrade in regards to Proxmox?

I've personally had weird, hard to debug issues related to tty handling with apt and I see that it still outputs the scripting warning:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

So I assume that as a general rule, apt-get dist-upgrade would still be the more stable, reliable choice?

 

[gfngfn256]

Doing updates is clearly documented in the docs.

I've personally had weird, hard to debug issues related to tty handling with apt and I see that it still outputs the scripting warning:

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

So I assume that as a general rule, apt-get dist-upgrade would still be the more stable, reliable choice?

That is not the exact reason - search these forums (& others) that will show you the possible damage/havoc that can be caused in PVE with apt upgrade

Just hope this thread doesn't turn into yet another upgrade/dist-upgrade rant!

 

[aj@root]

What I am thinking is before I join to the existing cluster I would like to upgrade those new nodes to the version 8.2.4 only to match with existing nodes.

PS: At the moment I cannot make any changes to existing 4 nodes which is running PVE 8.2.4.

Did you see the answers to your question? There are at least 4 options laid out:
- sync versions with dpkg
- standard CLI upgrade
- standard Web UI upgrade
- use apt mirrors for future upgrades

Will any of them work for you?

This thread took a bit of a sideways turn due to some outdated / incorrect information on my part, but I wanted to make sure that you didn't miss the possible resolutions to your actual problem amidst the back and forth.