Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
proxmox-kernel-6.8.8-1-pve-signed
The following packages will be upgraded:
libnvpair3linux libpve-cluster-api-perl libpve-cluster-perl
libpve-guest-common-perl libpve-notify-perl libpve-rs-perl libpve-storage-perl
libuutil3linux libzfs4linux libzpool5linux proxmox-kernel-6.8 pve-cluster
pve-container pve-esxi-import-tools pve-firmware pve-ha-manager pve-manager
shim-signed shim-signed-common spl zfs-initramfs zfs-zed zfsutils-linux
23 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 244 MB of archives.
After this operation, 582 MB of additional disk space will be used.
Do you want to continue? [Y/n]
Can confirm. Thank you and sorry about the game yesterdaypve-no-subscription repository should be fixed again.
if you followed the advice here and have installed proxmox-backup-client 3.2.5-1 to work around the warning, please be aware that that version has opt-in experimental features that might not yet be ready for prime time. unless you explicitly invoke vzdump or proxmox-backup-client with parameters to enable those features, it should still be safe.
Thanks, this worked for me on a fresh install over debian 12.Sir, you are super star. Worked great, node is back up.
Thanks Fabi!if you followed the advice here and have installed proxmox-backup-cli
pve-no-subscription repository should be fixed again.
if you followed the advice here and have installed proxmox-backup-client 3.2.5-1 to work around the warning, please be aware that that version has opt-in experimental features that might not yet be ready for prime time. unless you explicitly invoke vzdump or proxmox-backup-client with parameters to enable those features, it should still be safe.
workaround:
Bash:apt-mark hold proxmox-ve pve-manager apt update apt full-upgrade
when finaly fixed by staff:
Bash:apt-mark unhold proxmox-ve pve-manager apt update apt full-upgrade
Hi all,
There is no official statement that it is fixed, is there? I don't want to offend: just a question to maybe improve things. I suppose you have automated regression tests. Why is repository integrity of a "fresh install" not integrated into automated regression tests? I think it would be worth it for the only two outward-facing repositories.
Thanks for some insight from staff.
Thanks,
lopiuh
see reply by @Spaneta (and my linked earlier reply, in case you missed it).
such checks exist, they didn't cover a specific (rarely used) manual process that was the cause of yesterday's issue, they now (or soon will, the change is not yet deployed) cover that as well. and yes, an additional test that checks this from the outside would be a good addition as well.