[SOLVED] Moving from no-subscription to enterprise

[carles89]

Hello,

We've a 4 node cluster hosted in a cloud provider. All nodes have a basic subscription. Now we've acquired a new node, and the installation template from the hoster comes with the pve-no-subscription repository.

I know that I need to comment the pve-no-subscription entry at sources.list and then add the enterprise repo, but my question is:

Is it possible to "revert" all proxmox related packages that may have been installed from the no-subscription repo to the enterprise one?

Thank you

 

[H4R0]

If you switch to enterprise it will downgrade packages with the next upgrade in gui or via "apt update && apt full-upgrade"

 

[fabian]

If you switch to enterprise it will downgrade packages with the next upgrade in gui or via "apt update && apt full-upgrade"

that's not true - APT will only ever downgrade when you explicitly request it via pinning.

the expected course of action is to just leave the new node as-is after enabling the enterprise repo and disabling the no-subscription one. the enterprise repository will "catch up" with the installed state in a matter of days/weeks and start providing updates after that. alternatively, you can also install using the last iso and immediately enable enterprise before installing any updates - a non-beta iso will never have higher versions than the current enterprise repo, since the repos are synced through on ISO release.

 

[carles89]

Hi,

It seems not possible to install from the ISO. What we did in previous installation was to use a template from an old PVE, i.e. PVE5, then add the subscription and then upgrade to PVE6. We cannot do this because PVE5 template is not available anymore.

Here are the package versions that the new server has. Can we consider them stable for production use and for joining a cluster formed by nodes with an standard subscription?

proxmox-ve: 6.3-1 (running kernel: 5.4.103-1-pve)
pve-manager: 6.3-6 (running version: 6.3-6/2184247e)
pve-kernel-5.4: 6.3-7
pve-kernel-helper: 6.3-7
pve-kernel-5.4.103-1-pve: 5.4.103-1
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.1.0-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35
libjs-extjs: 6.0.1-10
libknet1: 1.20-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.3-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-5
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-7
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
proxmox-backup-client: 1.0.10-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-6
pve-cluster: 6.2-1
pve-container: 3.3-4
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.2-2
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.2.0-3
pve-xtermjs: 4.7.0-3
pve-zsync: 2.0-4
qemu-server: 6.3-8
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.3-pve2

Thank you

 

[fabian]

if you want to be 100% certain, you need to wait with joining until pve-enterprise has caught up (you can verify this by comparing "pveversion -v" output on the existing cluster and the new node). right now, pve-no-subscription has a newer Qemu (5.2 vs 5.1) and ZFS (2.0.3 vs 0.8.5) version, and at least for the former we have reports on some systems about instability (which is one reason why it hasn't been moved to pve-enterprise yet, since the exact cause is not clear yet).

 

[carles89]

Thank you for the clarification. I've opened a ticket with the provider asking if it's possible to install from PVE5 template. If so, I'll install PVE from it and then upgrade to PVE6 with the enterprise-repository.

If that's not possible, I'll try to mount the iso via IPMI and do the installation.

 

[carles89]

Hi,

Just for reference, I ended up installing the ISO via IPMI. Everything worked as expected.