Hi!
There was fine running licenced 22 hosts proxmox v. 6.3 cluster last year. And things proceeded this way that probably temporarily there are no licences to use i.e. licences are expired. Still, cluster runs fine. Because of several reasons i would like this cluster be upgraded so to say in-place-way to v. 6.4 and using no-subscription repository at the moment.
I followed this procedure, first on one node (this node uses separate ceph storage resource over network and openvswitch-switch)
0. pveversion -> pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve)
1. apt sources are like this now
2. apt-get update --allow-releaseinfo-change
3. apt-mark hold libnvpair1linux libuutil1linux libzfs2linux libzpool2linux proxmox-ve pve-firmware pve-kernel-5.4
4. apt-get dist-upgrade
5. apt-mark unhold libnvpair1linux libuutil1linux libzfs2linux libzpool2linux proxmox-ve pve-firmware pve-kernel-5.4
6. apt-get dist-upgrade
7. reboot
8. pveversion -> pve-manager/6.4-14/15e2bf61 (running kernel: 5.4.174-2-pve)
And after reboot everything seems running beautifully and dpkg -l \*pve\* shows pve v. 6.4 packages. This apt-mark hold and unhold was for some reason necessary otherwise it wanted to remove proxmox-ve and several other packages.
I would like to ask you if this would be appropriate procedure so far?
And since i have under 'webgui Host → Subscription' Expired subscription key (plus there is button Remove Subscription) how would be correct to handle this subscription part, i.e. to remove subscription keys on every node of cluster before beginning upgrading with before mentioned procedure; or leave this expired state be? Also, at some point in time i intend to again start buying subscription. Is there reason to worry that fiddling with subscription will break cluster, need reboot etc?
Thank you for your very fine software, best regards,
Imre
There was fine running licenced 22 hosts proxmox v. 6.3 cluster last year. And things proceeded this way that probably temporarily there are no licences to use i.e. licences are expired. Still, cluster runs fine. Because of several reasons i would like this cluster be upgraded so to say in-place-way to v. 6.4 and using no-subscription repository at the moment.
I followed this procedure, first on one node (this node uses separate ceph storage resource over network and openvswitch-switch)
0. pveversion -> pve-manager/6.3-3/eee5f901 (running kernel: 5.4.78-2-pve)
1. apt sources are like this now
# cat ceph.list
deb http://download.proxmox.com/debian/ceph-octopus buster main
# cat pve-enterprise.list
# deb https://enterprise.proxmox.com/debian/pve buster pve-enterprise
# cat pve-no-subscription.list
deb http://download.proxmox.com/debian/pve buster pve-no-subscription
2. apt-get update --allow-releaseinfo-change
3. apt-mark hold libnvpair1linux libuutil1linux libzfs2linux libzpool2linux proxmox-ve pve-firmware pve-kernel-5.4
4. apt-get dist-upgrade
5. apt-mark unhold libnvpair1linux libuutil1linux libzfs2linux libzpool2linux proxmox-ve pve-firmware pve-kernel-5.4
6. apt-get dist-upgrade
7. reboot
8. pveversion -> pve-manager/6.4-14/15e2bf61 (running kernel: 5.4.174-2-pve)
And after reboot everything seems running beautifully and dpkg -l \*pve\* shows pve v. 6.4 packages. This apt-mark hold and unhold was for some reason necessary otherwise it wanted to remove proxmox-ve and several other packages.
I would like to ask you if this would be appropriate procedure so far?
And since i have under 'webgui Host → Subscription' Expired subscription key (plus there is button Remove Subscription) how would be correct to handle this subscription part, i.e. to remove subscription keys on every node of cluster before beginning upgrading with before mentioned procedure; or leave this expired state be? Also, at some point in time i intend to again start buying subscription. Is there reason to worry that fiddling with subscription will break cluster, need reboot etc?
Thank you for your very fine software, best regards,
Imre
Last edited: