Hi,
Not ure about this particular situation, but you could try:
apt-get --with-new-pkgs upgrade
or otherwise you could try manually installing the kept-back packages with
apt-get install libpve-access-control libpve-common-perl ...
Perhaps that helps?
MJ
On 5/29/20 11:14 AM, Olivier Mascia wrote:
I'm seeing a discrepancy since my last round of upgrades (on a 4 nodes cluster).
My pve2/pve3/pve4 nodes all report :
Linux 5.4.41-1-pve #1 SMP PVE 5.4.41-1 (Fri, 15 May 2020 15:06:08 +0200)
pve-manager/6.2-4/9824574a
with (as writing this) no other updates available. Looks fine.
Yet one node (pve1) reports:
Linux 5.4.41-1-pve #1 SMP PVE 5.4.41-1 (Fri, 15 May 2020 15:06:08
+0200). [OK]
pve-manager/6.1-5/9bf06119 [DISCREPANCY]
Attempting an ordinary update from GUI or apt-get dist-upgrade returns this:
Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
libpve-access-control libpve-common-perl libpve-guest-common-perl
libpve-http-server-perl libpve-storage-perl lxc-pve pve-container
pve-manager
qemu-server
0 upgraded, 0 newly installed, 0 to remove and 9 not upgraded.
System not fully up to date (found 13 new packages)
I'm not experienced with this situation. What do you think (or better know!) I
should do?
Thanks a lot.
⏤
Best Regards, Meilleures salutations, Met vriendelijke groeten, Mit
freundlichen Grüßen,
Olivier Mascia
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
___
pve-user mailing list
pve-user@pve.proxmox.com
https://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user
