Accidentally upgraded 8.1.3 to 8.2.7 via "apt upgrade" - any potential issues?

Pyromancer

Member
Jan 25, 2021
29
7
8
48
I know the correct method for a Proxmox upgrade is apt-get update, then apt-get dist-upgrade. First I forgot it's meant to be apt-get, and then I managed to type "apt upgrade" when I'd meant to type "apt update". Realised my mistake straight away but as upgrade was running didn't want to stop it in case broke anything, so allowed it to complete, and then ran apt-get update and apt-get dist-upgrade. Neither command errored but they didn't install or remove anything either.

Rebooted the system and it's come up fine with the new version complete with shiny new ESXi storage/import option.

Is there anything I need to be wary of, or is this a minor enough upgrade that using the wrong method won't cause any issues?
 
apt is a wrapper for apt-get and that would not cause any problems in this case. I think running dist-upgrade after upgrade should fix any remaining upgrades (but there apparently weren't any). I think you're fine and would suggest doing this more often from now on.
 
  • Like
Reactions: Pyromancer
apt is a wrapper for apt-get and that would not cause any problems in this case. I think running dist-upgrade after upgrade should fix any remaining upgrades (but there apparently weren't any). I think you're fine and would suggest doing this more often from now on.
Thanks, appreciate the reply.

Always wary of running updates on production systems, just in case, but noted. Upgrading means migrating all the VMs to other hosts, upgrade one, and move them all back again, which does tend to take some time, hence we don't tend to do it more often than needed. But in this case we also have a fleet of VMware hosts we want to move VMs off and then shut down, to reduce power usage, so we need to upgrade the cluster to enable that.

We've already tested it on dev systems, where we successfully moved a CentOS VM from ESXi 6.0 to Proxmox, even though the announcement said only tested on 6.5 and above, so that was a pleasant bonus.
 
You're better off updating Proxmox hosts from the GUI, or write a script to do it the same way. Typing in stuff ad hoc at the command line can tangle you up, as you've seen.

As long as nothing new came in when you did it the right way, should be OK. But make sure to do it the recommended way in the future (and HAVE A FULL BACKUP before you mess around with ANY upgrades / system changes.)
 
  • Like
Reactions: Pyromancer

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!