Upgrading PVE Tries to Remove proxmox-ve package

[Spaneta]

workaround:

apt-mark hold proxmox-ve pve-manager
apt update
apt full-upgrade

when finaly fixed by staff:

apt-mark unhold proxmox-ve pve-manager

apt update

apt full-upgrade

Based on your idea I did ...

sudo apt-mark hold libpve-notify-perl

sudo apt update

Then ...

pme@vpe3:~$ sudo apt -o Debug::pkgProblemResolver=yes dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libpve-notify-perl:amd64 < 8.0.6 | 8.0.7 @hi pumH Ib >
Broken libpve-notify-perl:amd64 Depends on libpve-cluster-perl:amd64 < 8.0.6 -> 8.0.7 @ii umU > (= 8.0.6)
  Considering libpve-cluster-perl:amd64 39 as a solution to libpve-notify-perl:amd64 10006
  Added libpve-cluster-perl:amd64 to the remove list
  Fixing libpve-notify-perl:amd64 via keep of libpve-cluster-perl:amd64
 Try to Re-Instate (0) libpve-cluster-perl:amd64
Re-Instated libpve-cluster-perl:amd64 (1 vs 1)
Investigating (1) libpve-notify-perl:amd64 < 8.0.6 | 8.0.7 @hi pumH Ib >
Broken libpve-notify-perl:amd64 Depends on libpve-cluster-perl:amd64 < 8.0.6 -> 8.0.7 @ii umU > (= 8.0.6)
  Considering libpve-cluster-perl:amd64 39 as a solution to libpve-notify-perl:amd64 10006
  Added libpve-cluster-perl:amd64 to the remove list
  Fixing libpve-notify-perl:amd64 via keep of libpve-cluster-perl:amd64
Investigating (1) libpve-cluster-api-perl:amd64 < 8.0.6 -> 8.0.7 @ii umU Ib >
Broken libpve-cluster-api-perl:amd64 Depends on libpve-cluster-perl:amd64 < 8.0.6 | 8.0.7 @ii umH > (= 8.0.7)
  Considering libpve-cluster-perl:amd64 39 as a solution to libpve-cluster-api-perl:amd64 2
  Holding Back libpve-cluster-api-perl:amd64 rather than change libpve-cluster-perl:amd64
 Try to Re-Instate (2) libpve-cluster-api-perl:amd64
Done
Calculating upgrade... Done
The following NEW packages will be installed:
  proxmox-kernel-6.8.8-1-pve-signed
The following packages have been kept back:
  libpve-cluster-api-perl libpve-cluster-perl libpve-notify-perl libpve-rs-perl pve-container pve-manager
The following packages will be upgraded:
  libnvpair3linux libpve-guest-common-perl libpve-storage-perl libuutil3linux libzfs4linux libzpool5linux proxmox-kernel-6.8 pve-cluster pve-esxi-import-tools pve-firmware pve-ha-manager shim-signed shim-signed-common spl zfs-initramfs
  zfs-zed zfsutils-linux
17 upgraded, 1 newly installed, 0 to remove and 6 not upgraded.
Need to get 0 B/241 MB of archives.
After this operation, 582 MB of additional disk space will be used.
Do you want to continue? [Y/n]

Seems equivalent to your workaround to me but only hold 1 package and less warnings from apt -o ...
Will see if all is working as expected on this test Proxmox ...

 

[Ollie1979]

Also removed proxmox-ve and was missing the pveproxy.service and pveversion etc.

I was able to access with ssh my proxmox installation and restoring the previous pve-manager with:

apt install pve-manager=8.2.3

Afterwards I was able to login again.

 

[devrimer]

Also removed proxmox-ve and was missing the pveproxy.service and pveversion etc.

I was able to access with ssh my proxmox installation and restoring the previous pve-manager with:

apt install pve-manager=8.2.3

Afterwards I was able to login again.

thank you!

this is worked for me!

now I have access to GUI via serverip:8006

 

[Spaneta]

wget http://download.proxmox.com/debian/pve/dists/bookworm/pvetest/binary-amd64/proxmox-backup-client_3.2.5-1_amd64.deb
dpkg -i proxmox-backup-client_3.2.5-1_amd64.deb

That just unblocked my upgrade path, no guarantees it actually works though.

That said, my upgrade just completed, rebooted, and I'm logged back in through SSH, so I'm optimistic.

Excellent idea IMHO
Will test that on another test node ...

 

[gfngfn256]

Why are no staff chiming in here? This has become a multi-thread issue.

 

[leesteken]

Why are no staff chiming in here? This has become a multi-thread issue.

It's not office hours. I guess we have to wait until morning in Austria.

 

[rafael.maldonado77]

wget http://download.proxmox.com/debian/pve/dists/bookworm/pvetest/binary-amd64/proxmox-backup-client_3.2.5-1_amd64.deb
dpkg -i proxmox-backup-client_3.2.5-1_amd64.deb

That just unblocked my upgrade path, no guarantees it actually works though.

That said, my upgrade just completed, rebooted, and I'm logged back in through SSH, so I'm optimistic.

This worked for me too. Thanks!

 

[dokkenrolf]

It's not office hours. I guess we have to wait until morning in Austria.

And don't forget the UEFA European Championsship Soccer game France-Austria actually now.

 

[leesteken]

And don't forget the UEFA European Championsship Soccer game France-Austria actually now.

Who cares about people getting money to kick a ball and to get other people to watch advertisements?

 

[Datajock]

Alternative method to get working again.

Add the pvetest repository to /etc/apt/sources.list or via the UI.
Then

apt-get install proxmox-backup-client

After that, you can disable the pvetest repository and do the normal apt-get update ; apt-get dist-upgrade and have it work.

At least that worked for me.

I had just installed from a fresh download of the latest ISO and tried doing the upgrade from there. So, a fresh install will not help anyone having the issue.

 

[devrimer]

my promox was 8.2.2
after some update it become 8.2.3
after reboot it become 8.2.4

but anyway I updated everything. there is no update in the update section.
and I have access to GUI.

 

[DanH]

Same issue here too.
Looking forward for a fix.
In the meantime, how can I contribute?

 

[Dunuin]

I run those commands:

apt-get update
apt update
apt list --upgradable
apt upgrade
apt full-upgrade

Again, never run "apt upgrade" or it might break stuff. And DONT run that "touch '/please-remove-proxmox-ve'".

 

[ravenssettle]

Again, never run "apt upgrade" or it might break stuff. And DONT run that "touch '/please-remove-proxmox-ve'".

Forgive the newbish question: how/why does apt upgrade break things?

 

[kiwinho]

ok for me:

wget http://download.proxmox.com/debian/pve/dists/bookworm/pvetest/binary-amd64/proxmox-backup-client_3.2.5-1_amd64.deb
dpkg -i proxmox-backup-client_3.2.5-1_amd64.deb

 

[Dunuin]

Forgive the newbish question: how/why does apt upgrade break things?

It won't check/resolve dependency problems. It will upgrade stuff and then you are stuck with incompatible versions. Only apt dist-upgrade and apt full-upgrade are safe.

 

[pagalba-com]

+1
football must be the reason, guys where very hurry to go to see the match

 

[DanH]

Sir, you are super star. Worked great, node is back up.

wget http://download.proxmox.com/debian/pve/dists/bookworm/pvetest/binary-amd64/proxmox-backup-client_3.2.5-1_amd64.deb
dpkg -i proxmox-backup-client_3.2.5-1_amd64.deb

That just unblocked my upgrade path, no guarantees it actually works though.

That said, my upgrade just completed, rebooted, and I'm logged back in through SSH, so I'm optimistic.

That fixed it for me too.
I only upgraded one of the test nodes that way. I wait wait the other 2 in that cluster until the official fix is coming.
I guess..

 

[tteckster]

The test repository does not have this issue, only the no-subscription.

 

[grayfox404]

Also removed proxmox-ve and was missing the pveproxy.service and pveversion etc.

I was able to access with ssh my proxmox installation and restoring the previous pve-manager with:

apt install pve-manager=8.2.3

Afterwards I was able to login again.

yeah this jsut fucked my day up, thank you!!!!!!!!!!