Recovering from apt-get upgrade?

[zebb]

Hi all,

I usually update my proxmox hosts (currently running ProxMox 7) via the web interface, but decided to update them via ssh while out of the office.

Carelessly, I didn't read the documentation until after the first one, and went for my standard

apt-get update
apt-get upgrade

According to previous posts, this is a bad plan, and can break things. Having read the documentation after the fact, I immediately followed it with the recommended

apt-get dist-upgrade

and have not rebooted.

Things appear to be functioning normally for now, but I'd appreciate some advice on:

• How does `apt-get upgrade` break things?
• Is there anything I can do at this point to fix things?
• How would I verify that I have (or haven't) broken my system?

 

[Dunuin]

How does `apt-get update` break things?

Dependencies won't be resolved as it wont remove packages even if that means dependencies won't be met anymore. See the apt-get manual:

upgrade
Used to install the newest versions of all packages currently installed on the system from the sources enumerated in /etc/apt/sources.list(5). Packages currently installed with new versions available are retrieved and upgraded; under no circumstances are currently installed packages removed, nor are packages that are not already installed retrieved and installed. New versions of currently installed packages that cannot be upgraded without changing the install status of another package will be left at their current version. An update must be performed first so that apt-get knows that new versions of packages are available.

dist-upgrade
In addition to performing the function of upgrade, this option also intelligently handles changing dependencies with new versions of packages; apt-get has a "smart" conflict resolution system, and it will attempt to upgrade the most important packages at the expense of less important ones, if necessary.

 

[zebb]

Thanks!

Comparing the problem machine's apt/history.log with an identical box that went straight to `apt-get dist-upgrade`, I think I've dodged a bullet:

`apt-get update
apt-get upgrade
apt-get dist-upgrade`

Commandline: apt-get upgrade
Upgrade: libcurl4:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), openssh-client:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), tzdata:amd64 (2021a-1+deb11u10, 2021a-1+deb11u11), zfs-zed:amd64 (2.1.11-pve1, 2.1.14-pve1), zfs-initramfs:amd64 (2.1.11-pve1, 2.1.14-pve1), spl:amd64 (2.1.11-pve1, 2.1.14-pve1), ssh:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), libnvpair3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libuutil3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libzpool5linux:amd64 (2.1.11-pve1, 2.1.14-pve1), openssh-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), proxmox-backup-file-restore:amd64 (2.4.3-1, 2.4.4-1), proxmox-backup-client:amd64 (2.4.3-1, 2.4.4-1), openssh-sftp-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), libzfs4linux:amd64 (2.1.11-pve1, 2.1.14-pve1), curl:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), zfsutils-linux:amd64 (2.1.11-pve1, 2.1.14-pve1)


Commandline: apt-get dist-upgrade
Install: pve-kernel-5.15.131-2-pve:amd64 (5.15.131-3, automatic)
Upgrade: pve-kernel-5.15:amd64 (7.4-7, 7.4-9)

`apt-get update
apt-get dist-upgrade`

Commandline: apt dist-upgrade
Install: pve-kernel-5.15.131-2-pve:amd64 (5.15.131-3, automatic)
Upgrade: libcurl4:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), openssh-client:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), tzdata:amd64 (2021a-1+deb11u10, 2021a-1+deb11u11), zfs-zed:amd64 (2.1.11-pve1, 2.1.14-pve1), zfs-initramfs:amd64 (2.1.11-pve1, 2.1.14-pve1), spl:amd64 (2.1.11-pve1, 2.1.14-pve1), ssh:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), libnvpair3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libuutil3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libzpool5linux:amd64 (2.1.11-pve1, 2.1.14-pve1), openssh-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), proxmox-backup-file-restore:amd64 (2.4.3-1, 2.4.4-1), proxmox-backup-client:amd64 (2.4.3-1, 2.4.4-1), openssh-sftp-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), pve-kernel-5.15:amd64 (7.4-7, 7.4-9), libzfs4linux:amd64 (2.1.11-pve1, 2.1.14-pve1), curl:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), zfsutils-linux:amd64 (2.1.11-pve1, 2.1.14-pve1)

Those appear to be functionally equivalent, with no removes.

 

[esi_y]

Thanks!

Comparing the problem machine's apt/history.log with an identical box that went straight to `apt-get dist-upgrade`, I think I've dodged a bullet:

`apt-get update
apt-get upgrade
apt-get dist-upgrade`

Commandline: apt-get upgrade
Upgrade: libcurl4:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), openssh-client:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), tzdata:amd64 (2021a-1+deb11u10, 2021a-1+deb11u11), zfs-zed:amd64 (2.1.11-pve1, 2.1.14-pve1), zfs-initramfs:amd64 (2.1.11-pve1, 2.1.14-pve1), spl:amd64 (2.1.11-pve1, 2.1.14-pve1), ssh:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), libnvpair3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libuutil3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libzpool5linux:amd64 (2.1.11-pve1, 2.1.14-pve1), openssh-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), proxmox-backup-file-restore:amd64 (2.4.3-1, 2.4.4-1), proxmox-backup-client:amd64 (2.4.3-1, 2.4.4-1), openssh-sftp-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), libzfs4linux:amd64 (2.1.11-pve1, 2.1.14-pve1), curl:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), zfsutils-linux:amd64 (2.1.11-pve1, 2.1.14-pve1)


Commandline: apt-get dist-upgrade
Install: pve-kernel-5.15.131-2-pve:amd64 (5.15.131-3, automatic)
Upgrade: pve-kernel-5.15:amd64 (7.4-7, 7.4-9)

`apt-get update
apt-get dist-upgrade`

Commandline: apt dist-upgrade
Install: pve-kernel-5.15.131-2-pve:amd64 (5.15.131-3, automatic)
Upgrade: libcurl4:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), libcurl3-gnutls:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), openssh-client:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), tzdata:amd64 (2021a-1+deb11u10, 2021a-1+deb11u11), zfs-zed:amd64 (2.1.11-pve1, 2.1.14-pve1), zfs-initramfs:amd64 (2.1.11-pve1, 2.1.14-pve1), spl:amd64 (2.1.11-pve1, 2.1.14-pve1), ssh:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), libnvpair3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libuutil3linux:amd64 (2.1.11-pve1, 2.1.14-pve1), libzpool5linux:amd64 (2.1.11-pve1, 2.1.14-pve1), openssh-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), proxmox-backup-file-restore:amd64 (2.4.3-1, 2.4.4-1), proxmox-backup-client:amd64 (2.4.3-1, 2.4.4-1), openssh-sftp-server:amd64 (1:8.4p1-5+deb11u2, 1:8.4p1-5+deb11u3), pve-kernel-5.15:amd64 (7.4-7, 7.4-9), libzfs4linux:amd64 (2.1.11-pve1, 2.1.14-pve1), curl:amd64 (7.74.0-1.3+deb11u10, 7.74.0-1.3+deb11u11), zfsutils-linux:amd64 (2.1.11-pve1, 2.1.14-pve1)

Those appear to be functionally equivalent, with no removes.

There was this "blanket" answer on that some time ago:
https://forum.proxmox.com/threads/n...m-host-is-pve-8-0-4.132620/page-2#post-617127

Unfortunately, there's no good explanation why more had not been done to prevent this from happening to someone like you (and many more in the future).

Could it be something needs the new kernel?

 

[esi_y]

Things appear to be functioning normally for now, but I'd appreciate some advice on:

In case I had misread you (I think I did), in this particular instance, no difference for you between the two.