Can i prevent mixed 6/7 PVE cluster from changing storage/backup config to the new version?

[gradinaruvasile]

Hello.
We have a 5 member cluster that originally had been 3 servers running PVE 6.1. Now we added 2 more servers that were installed with the latest, 7.3 at that time. The idea is to upgrade gradually and the new servers were to test the compatibility between versions.
Unfortunately there were unforseen side effects if someone logged into the new servers and edited backup schedules, those were moved to the /etc/pve/jobs.cfg file instead of the old /etc/pve/vzdum.cron causing the old servers to miss schedules. Also storage configs if edited on new servers had a different syntax and the backup retention is reset to 1 on the old servers causing mass backup deletions.
Besides asking nicely everyone to use only the old servers for such operations, is there any option on the PVE 7 series to retain backwards compatible operations like using old style storage configs until the old servers are upgraded?

 

[bbgeek17]

As far as I know there is no option that you can flip to stop changes that are version specific.
Good practices, when running any software cluster with different versions is to treat it as Read Only system, even if thats not enforced by the system itself.
Very few, if any vendors, officially support running a mis-versioned cluster. As official support would imply that this is being tested. As you can imagine testing across every possible revision combination is prohibitively expensive, both monetary and time wise. PVE is definitely not one of those few who officially endorse this.
Any configuration change you do now could be a breaking change. If you were planning this before upgrade, I'd say - create an account for anyone who can touch the system and remove any write permissions from those accounts.

At this point you goal should be to finish the upgrade as soon as possible.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox