can't upgrade 5.1 -> 5.2 using dist-upgrade

[charles.u]

Long time sysadmin here, I'm missing something so obvious that I'm going to kick myself once someone shows me what it is.

I have a Proxmox VE 5.1 system that I installed from media some time ago. I'd like to upgrade it to 5.2. Everything I've read so far says that this is as simple as "apt update && apt dist-upgrade".

The "apt update" works just fine, and normal debian packages upgrade as they should, but the proxmox packages never get touched.

I can't show you my sources because I'm a new user and am not allowed to post URLs. But rest assured they match exactly what is in the wiki on the Downloads page.

I have no packages held:

# apt-mark showhold
#

I am using a proxy because this host does not have direct access to the internet. However, I have tried switching proxies (one of them is an apt cache, one of them is a general-purpose proxy) to no effect. Also, I have no problems using either proxy with any other Debian host (and there are a lot!).

Finally, I am able to install packages just fine with "apt install foo".

Edit: Almost forgot, pveversion:

# pveversion -v
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90


This one has me stumped. Any suggestions?

 

[ChristopherG]

Hi,
Did you try cli "apt full-upgrade"?

 

[tom]

Long time sysadmin here, I'm missing something so obvious that I'm going to kick myself once someone shows me what it is.

See https://pve.proxmox.com/wiki/Package_Repositories

 

[charles.u]

Okay, so I think what was going on here was that I had a fundamental misunderstanding of how Proxmox licensing and upgrades work.

I was under the impression that even without a paid license, you could simply do "apt update && apt dist-upgrade" to upgrade your version of Proxmox. This does not appear to be the case. Unless you actively go and modify the sources list, the version of Proxmox that you install from media will be the version you have forever. Or pay for licensing, or wipe and reinstall from updated media. What threw me for a loop here was that the enterprise repo was enabled by default and yet "apt" reported no errors when updating.

Mystery solved!