Upgrade Proxmox VE 6.4 No-Subscription to 7.x Enterprise Repository

[wolke23]

Hello,

What's the better way to do an in-place upgrade to end up with a 7.x host with a subscription coming from a 6.4 non-subscription installation:

1. activate the key and switch to the enterprise repository first, and then do the upgrade
2. do the 6 to 7 upgrade while staying on the non-subscription repo and activate the key/enterprise repo after the upgrade

Thanks!

 

[leesteken]

The main feature of the enterprise repository is that it has older packages (which are more tested) than the no-subscription one. Therefore, I would suggest 1 instead of 2. However, I have no experience with the in-place upgrade from 6.4 to 7.

 

[pvps1]

we are looking forward to the same process.
additional "problem" is, that we wont migrate all hosts of the existing cluster and retire some of the older hosts. so fo some time, we would have a mixed cluster licensed/unlicensed.

still unsure what way to go. hints/tips?

 

[fabian]

the main things to be aware of
- to get enterprise support for a node in a cluster, the whole cluster needs to have the required subscription level active
- features or changes introduced in newer versions are sometimes not compatible with older ones, which could affect things like backup/restore or migration from no-subscription to enterprise nodes (since the latter have slightly "older" packages usually)

we try to keep the fallout small for the second part, but sometimes it's unavoidable. old to new should always work and would be considered a bug within a major version if it doesn't

 

[wolke23]

Thanks for your answers!

 

[pvps1]

the main things to be aware of
- to get enterprise support for a node in a cluster, the whole cluster needs to have the required subscription level active
- features or changes introduced in newer versions are sometimes not compatible with older ones, which could affect things like backup/restore or migration from no-subscription to enterprise nodes (since the latter have slightly "older" packages usually)

we try to keep the fallout small for the second part, but sometimes it's unavoidable. old to new should always work and would be considered a bug within a major version if it doesn't

thx. the destination is a fully licenced cluster anyway.

the open question was "when" to do the licensing of the new cluster hosts (that will stay while the oldest ones will drop out).

 

[fabian]

if you want to keep the cluster nodes all on the same version you need to configure them all with the no-subscription repository. when you then switch the remaining ones to enterprise, they will take a few days or weeks until the enterprise repository has caught up with the state of no-subscription, but there's no harm in that.

if you don't care about keeping them all at the same version, you can switch the ones that will stay to enterprise already now.