Upgrade from 3.4 to 4.4

SaAtomic

Member
Jan 11, 2017
5
0
21
125
I'm planning an in-place upgrade from Prxomox VE 3.4 to 4.4 of one node (no cluster). I've read trough the corresponding wiki entry and wanted to ask how risky it is in comparison to the new installation.

I'm hosting only two Ubuntu VMs, no CTs and the downtime during the upgrade shouldn't pose a problem. I don't use a custom setup nor do I have additional sources for software on the Proxmox host.

If I strictly follow the wiki, how likely will there be issues with the upgrade?
 
Last edited:
Hi,

if you have no extra repositories and no custom installation the risk in very low.
The only problems what can occur is,
if you have installed manually programs which can't be handled by systemd at the upgrade.

I tested the latest version 3.4 to 4.4 without problems.
Plain PVE installation on lvm ext4 and used kernel 4.4.35-2-pve.
 
Hi,

if you have no extra repositories and no custom installation the risk in very low.
The only problems what can occur is,
if you have installed manually programs which can't be handled by systemd at the upgrade.

I tested the latest version 3.4 to 4.4 without problems.
Plain PVE installation on lvm ext4 and used kernel 4.4.35-2-pve.

Thank you for the swift reply!

Does it pose a problem, that the update of the sources currently fails to fetch data from one source?

[...]
Ign https://enterprise.proxmox.com wheezy Release
Err https://enterprise.proxmox.com wheezy/pve-enterprise amd64 Packages
The requested URL returned error: 401
Ign https://enterprise.proxmox.com wheezy/pve-enterprise Translation-en
W: Failed to fetch https://enterprise.proxmox.com/debian/dists/wheezy/pve-enterprise/binary-amd64/Packages The requested URL returned error: 401

E: Some index files failed to download. They have been ignored, or old ones used instead.
TASK ERROR: command 'apt-get update' failed: exit code 100
 
Correct you have to use wheezy pve-no-subscription upgrade to 3.4 and reboot.

Then you can upgrade to PVE4.4
 
Worked as intended, but I had an issue is zfs, similar to the issue in another thread (see this thread). I had to manually import the rpool on boot.

Thanks for the assistance!