v7 to v8 upgrade issue

B

bellocarico

Member
Sep 17, 2022
48
3
13
I did a bit of reading and managed to upgrade v7 to 8 on two devices.
For some reason the second device didn't work as expected so I'm trying to work out what went wrong. Any help/suggestion you might have would be greatly appreciated.

# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian bookworm main contrib
deb http://ftp.debian.org/debian bookworm-updates main contrib
deb http://security.debian.org/debian-security bookworm-security main contrib
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
# deb http://download.proxmox.com/debian/pve bookworm pvetest
Click to expand...

# cat /etc/apt/sources.list.d/linux.dell.com.sources.list
deb http://linux.dell.com/repo/community/openmanage/10300/focal/ focal main
Click to expand...

# pveversion
pve-manager/8.0.4/d258a813cfa6b390 (running kernel: 6.2.16-12-pve)
Click to expand...

# apt update
Hit:1 http://security.debian.org/debian-security bookworm-security InRelease
Hit:2 http://download.proxmox.com/debian/pve bookworm InRelease
Hit:3 http://ftp.debian.org/debian bookworm InRelease
Hit:5 http://ftp.debian.org/debian bookworm-updates InRelease
Hit:4 https://linux.dell.com/repo/community/openmanage/10300/focal focal InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
24 packages can be upgraded. Run 'apt list --upgradable' to see them.
W: http://linux.dell.com/repo/community/openmanage/10300/focal/dists/focal/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.
Click to expand...

# apt list --upgradable
Listing... Done
ifupdown2/stable 3.2.0-1+pmx4 all [upgradable from: 3.1.0-1+pmx4]
libldb2/stable-security 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 amd64 [upgradable from: 2:2.2.3-2~deb11u2]
libpython3-stdlib/stable 3.11.2-1+b1 amd64 [upgradable from: 3.9.2-3]
libsemanage-common/stable 3.4-1 all [upgradable from: 3.1-1]
libsmbclient/stable-security 2:4.17.10+dfsg-0+deb12u1 amd64 [upgradable from: 2:4.13.13+dfsg-1~deb11u5]
libtalloc2/stable 2.4.0-f2 amd64 [upgradable from: 2.3.1-2+b1]
libtevent0/stable 0.14.1-1 amd64 [upgradable from: 0.10.2-1]
libwbclient0/stable-security 2:4.17.10+dfsg-0+deb12u1 amd64 [upgradable from: 2:4.13.13+dfsg-1~deb11u5]
nfs-common/stable 1:2.6.2-4 amd64 [upgradable from: 1:1.3.4-6]
passwd/stable 1:4.13+dfsg1-1+b1 amd64 [upgradable from: 1:4.8.1-1]
python3-apt/stable 2.6.0 amd64 [upgradable from: 2.2.1]
python3-cffi-backend/stable 1.15.1-5+b1 amd64 [upgradable from: 1.14.5-1]
python3-ldb/stable-security 2:2.6.2+samba4.17.10+dfsg-0+deb12u1 amd64 [upgradable from: 2:2.2.3-2~deb11u2]
python3-markupsafe/stable 2.1.2-1+b1 amd64 [upgradable from: 1.1.1-1+b3]
python3-minimal/stable 3.11.2-1+b1 amd64 [upgradable from: 3.9.2-3]
python3-protobuf/stable 3.21.12-3 amd64 [upgradable from: 3.12.4-1]
python3-pycurl/stable 7.45.2-3 amd64 [upgradable from: 7.43.0.6-5]
python3-talloc/stable 2.4.0-f2 amd64 [upgradable from: 2.3.1-2+b1]
python3-yaml/stable 6.0-3+b2 amd64 [upgradable from: 5.3.1-5]
python3/stable 3.11.2-1+b1 amd64 [upgradable from: 3.9.2-3]
samba-common/stable-security 2:4.17.10+dfsg-0+deb12u1 all [upgradable from: 2:4.13.13+dfsg-1~deb11u5]
samba-libs/stable-security 2:4.17.10+dfsg-0+deb12u1 amd64 [upgradable from: 2:4.13.13+dfsg-1~deb11u5]
smbclient/stable-security 2:4.17.10+dfsg-0+deb12u1 amd64 [upgradable from: 2:4.13.13+dfsg-1~deb11u5]
uidmap/stable 1:4.13+dfsg1-1+b1 amd64 [upgradable from: 1:4.8.1-1]
Click to expand...


# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libjaeger libjs-sencha-touch libslirp0 liburing2 proxmox-default-kernel proxmox-kernel-helper proxmox-mail-forward proxmox-offline-mirror-docs
proxmox-offline-mirror-helper
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
ceph-base ceph-common libnfsidmap2 libpve-guest-common-perl libpve-storage-perl libsemanage1 proxmox-ve pve-container pve-ha-manager pve-manager
pve-qemu-kvm python3-cephfs python3-rados python3-rbd python3-rgw qemu-server spiceterm
The following NEW packages will be installed:
libevent-core-2.1-7 libnfsidmap1 libprotobuf32 libpython3.11 libpython3.11-minimal libpython3.11-stdlib libsemanage2 libsepol2 libsubid4
python3-distutils python3-lib2to3 python3-setuptools python3-systemd python3.11 python3.11-minimal
The following packages will be upgraded:
ifupdown2 libldb2 libpython3-stdlib libsemanage-common libsmbclient libtalloc2 libtevent0 libwbclient0 nfs-common passwd python3 python3-apt
python3-cffi-backend python3-ldb python3-markupsafe python3-minimal python3-protobuf python3-pycurl python3-talloc python3-yaml samba-common
samba-libs smbclient uidmap
24 upgraded, 15 newly installed, 17 to remove and 0 not upgraded.
Need to get 0 B/18.8 MB of archives.
After this operation, 398 MB disk space will be freed.
Do you want to continue? [Y/n] y
W: (pve-apt-hook) !! WARNING !!
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
W: (pve-apt-hook)
W: (pve-apt-hook) If you really want to permanently remove 'proxmox-ve' from your system, run the following command
W: (pve-apt-hook) touch '/please-remove-proxmox-ve'
W: (pve-apt-hook) run apt purge proxmox-ve to remove the meta-package
W: (pve-apt-hook) and repeat your apt invocation.
W: (pve-apt-hook)
W: (pve-apt-hook) If you are unsure why 'proxmox-ve' would be removed, please verify
W: (pve-apt-hook) - your APT repository settings
W: (pve-apt-hook) - that you are using 'apt full-upgrade' to upgrade your system
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (1)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
Click to expand...

# ls -l /usr/share/proxmox-ve/pve-apt-hook
-rwxr-xr-x 1 root root 3576 Sep 15 12:33 /usr/share/proxmox-ve/pve-apt-hook
Click to expand...
 
Last edited:
# cat /etc/apt/sources.list.d/linux.dell.com.sources.list
deb http://linux.dell.com/repo/community/openmanage/10300/focal/ focal main
Click to expand...
Not sure what this repository contains, but please be aware that PVE is not based on Ubuntu focal, which this repo seems to expect. Since you also get deprecation warnings for it, you may want to remove it or find a more suitable repository for the packages it provides.

You may want to check out the upgrade guide and make sure it's not the problem mentioned there first: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Upgrade_wants_to_remove_package_.27proxmox-ve.27
 
sterzy said:
Not sure what this repository contains, but please be aware that PVE is not based on Ubuntu focal, which this repo seems to expect. Since you also get deprecation warnings for it, you may want to remove it or find a more suitable repository for the packages it provides.

You may want to check out the upgrade guide and make sure it's not the problem mentioned there first: https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Upgrade_wants_to_remove_package_.27proxmox-ve.27
Click to expand...
Thanks the dell repo is the interface to my raid controller Dell H700 software so that I can verify remotely if there's any issue with the underpinning storage.

Beside this:
# apt remove linux-image-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'linux-image-amd64' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 24 not upgraded.
Click to expand...
 
Still nothing here... does the output of the below command provide the necessary info for someone to help here?
Thanks!

Code: 
# apt -o Debug::pkgProblemResolver=yes dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Starting pkgProblemResolver with broken count: 7
Starting 2 pkgProblemResolver with broken count: 7
Investigating (0) python3-rados:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rados:amd64 Depends on python3:amd64 < 3.9.2-3 -> 3.11.2-1+b1 @ii umU > (< 3.10)
  Considering python3:amd64 101 as a solution to python3-rados:amd64 2
  Removing python3-rados:amd64 rather than change python3:amd64
Investigating (0) python3-rbd:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rbd:amd64 Depends on python3:amd64 < 3.9.2-3 -> 3.11.2-1+b1 @ii umU > (< 3.10)
  Considering python3:amd64 101 as a solution to python3-rbd:amd64 0
  Removing python3-rbd:amd64 rather than change python3:amd64
Investigating (0) python3-rgw:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rgw:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 2 as a solution to python3-rgw:amd64 0
  Removing python3-rgw:amd64 rather than change python3-rados:amd64
Investigating (0) libnfsidmap1:amd64 < none -> 1:2.6.2-4 @un uN Ib >
Broken libnfsidmap1:amd64 Conflicts on libnfsidmap2:amd64 < 0.25-6 @ii mK Ib >
  Considering libnfsidmap2:amd64 -4 as a solution to libnfsidmap1:amd64 0
  Added libnfsidmap2:amd64 to the remove list
Broken libnfsidmap1:amd64 Breaks on libnfsidmap2:amd64 < 0.25-6 @ii mK Ib > (< 0.25-7~)
  Considering libnfsidmap2:amd64 -4 as a solution to libnfsidmap1:amd64 0
  Added libnfsidmap2:amd64 to the remove list
  Fixing libnfsidmap1:amd64 via remove of libnfsidmap2:amd64
  Fixing libnfsidmap1:amd64 via remove of libnfsidmap2:amd64
Investigating (0) python3-cephfs:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-cephfs:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 2 as a solution to python3-cephfs:amd64 0
  Removing python3-cephfs:amd64 rather than change python3-rados:amd64
Investigating (0) libsemanage1:amd64 < 3.1-1+b2 @ii mK Ib >
Broken libsemanage1:amd64 Depends on libsemanage-common:amd64 < 3.1-1 -> 3.4-1 @ii umU > (= 3.1-1)
  Considering libsemanage-common:amd64 2 as a solution to libsemanage1:amd64 -2
  Removing libsemanage1:amd64 rather than change libsemanage-common:amd64
Investigating (1) ceph-common:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken ceph-common:amd64 Depends on python3-cephfs:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-cephfs:amd64 0 as a solution to ceph-common:amd64 9
  Added python3-cephfs:amd64 to the remove list
Broken ceph-common:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 2 as a solution to ceph-common:amd64 9
  Added python3-rados:amd64 to the remove list
Broken ceph-common:amd64 Depends on python3-rbd:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rbd:amd64 0 as a solution to ceph-common:amd64 9
  Added python3-rbd:amd64 to the remove list
Broken ceph-common:amd64 Depends on python3-rgw:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rgw:amd64 0 as a solution to ceph-common:amd64 9
  Added python3-rgw:amd64 to the remove list
  Fixing ceph-common:amd64 via keep of python3-cephfs:amd64
  Fixing ceph-common:amd64 via keep of python3-rados:amd64
  Fixing ceph-common:amd64 via keep of python3-rbd:amd64
  Fixing ceph-common:amd64 via keep of python3-rgw:amd64
Investigating (1) python3-rados:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rados:amd64 Depends on python3:amd64 < 3.9.2-3 -> 3.11.2-1+b1 @ii umU > (< 3.10)
  Considering python3:amd64 101 as a solution to python3-rados:amd64 2
  Removing python3-rados:amd64 rather than change python3:amd64
Investigating (1) python3-rbd:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rbd:amd64 Depends on python3:amd64 < 3.9.2-3 -> 3.11.2-1+b1 @ii umU > (< 3.10)
  Considering python3:amd64 101 as a solution to python3-rbd:amd64 0
  Removing python3-rbd:amd64 rather than change python3:amd64
Investigating (1) python3-rgw:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rgw:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 2 as a solution to python3-rgw:amd64 0
  Removing python3-rgw:amd64 rather than change python3-rados:amd64
Investigating (1) python3-cephfs:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-cephfs:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 2 as a solution to python3-cephfs:amd64 0
  Removing python3-cephfs:amd64 rather than change python3-rados:amd64
Investigating (2) ceph-common:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken ceph-common:amd64 Depends on python3-cephfs:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-cephfs:amd64 0 as a solution to ceph-common:amd64 9
  Added python3-cephfs:amd64 to the remove list
Broken ceph-common:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 2 as a solution to ceph-common:amd64 9
  Added python3-rados:amd64 to the remove list
Broken ceph-common:amd64 Depends on python3-rbd:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rbd:amd64 0 as a solution to ceph-common:amd64 9
  Added python3-rbd:amd64 to the remove list
Broken ceph-common:amd64 Depends on python3-rgw:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rgw:amd64 0 as a solution to ceph-common:amd64 9
  Added python3-rgw:amd64 to the remove list
  Fixing ceph-common:amd64 via keep of python3-cephfs:amd64
  Fixing ceph-common:amd64 via keep of python3-rados:amd64
  Fixing ceph-common:amd64 via keep of python3-rbd:amd64
  Fixing ceph-common:amd64 via keep of python3-rgw:amd64
Investigating (2) python3-rados:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rados:amd64 Depends on python3:amd64 < 3.9.2-3 -> 3.11.2-1+b1 @ii umU > (< 3.10)
  Considering python3:amd64 101 as a solution to python3-rados:amd64 9
  Removing python3-rados:amd64 rather than change python3:amd64
Investigating (2) python3-rbd:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rbd:amd64 Depends on python3:amd64 < 3.9.2-3 -> 3.11.2-1+b1 @ii umU > (< 3.10)
  Considering python3:amd64 101 as a solution to python3-rbd:amd64 9
  Removing python3-rbd:amd64 rather than change python3:amd64
Investigating (2) python3-rgw:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-rgw:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 101 as a solution to python3-rgw:amd64 9
  Removing python3-rgw:amd64 rather than change python3-rados:amd64
Investigating (2) python3-cephfs:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken python3-cephfs:amd64 Depends on python3-rados:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-rados:amd64 101 as a solution to python3-cephfs:amd64 9
  Removing python3-cephfs:amd64 rather than change python3-rados:amd64
Investigating (3) ceph-common:amd64 < 16.2.13-pve1 @ii mK Ib >
Broken ceph-common:amd64 Depends on python3-cephfs:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering python3-cephfs:amd64 101 as a solution to ceph-common:amd64 9
  Removing ceph-common:amd64 rather than change python3-cephfs:amd64
Investigating (3) ceph-base:amd64 < 16.2.13-pve1 @ii mK NPb Ib >
Broken ceph-base:amd64 Depends on ceph-common:amd64 < 16.2.13-pve1 @ii mR > (= 16.2.13-pve1)
  Considering ceph-common:amd64 101 as a solution to ceph-base:amd64 -2
  Removing ceph-base:amd64 rather than change ceph-common:amd64
Investigating (4) libpve-storage-perl:amd64 < 8.0.2 @ii mK Ib >
Broken libpve-storage-perl:amd64 Depends on ceph-common:amd64 < 16.2.13-pve1 @ii mR > (>= 12.2~)
  Considering ceph-common:amd64 101 as a solution to libpve-storage-perl:amd64 13
  Removing libpve-storage-perl:amd64 rather than change ceph-common:amd64
Investigating (4) pve-qemu-kvm:amd64 < 8.0.2-5 -> 8.0.2-6 @ii umU Ib >
Broken pve-qemu-kvm:amd64 Depends on ceph-common:amd64 < 16.2.13-pve1 @ii mR > (>= 0.48)
  Considering ceph-common:amd64 101 as a solution to pve-qemu-kvm:amd64 11
  Removing pve-qemu-kvm:amd64 rather than change ceph-common:amd64
Investigating (4) libpve-guest-common-perl:amd64 < 5.0.4 @ii mK Ib >
Broken libpve-guest-common-perl:amd64 Depends on libpve-storage-perl:amd64 < 8.0.2 @ii mR > (>= 7.0-14)
  Considering libpve-storage-perl:amd64 101 as a solution to libpve-guest-common-perl:amd64 9
  Removing libpve-guest-common-perl:amd64 rather than change libpve-storage-perl:amd64
Investigating (4) qemu-server:amd64 < 8.0.7 @ii mK Ib >
Broken qemu-server:amd64 Depends on libpve-guest-common-perl:amd64 < 5.0.4 @ii mR > (>= 5.0.3)
  Considering libpve-guest-common-perl:amd64 101 as a solution to qemu-server:amd64 7
  Removing qemu-server:amd64 rather than change libpve-guest-common-perl:amd64
Investigating (4) pve-container:amd64 < 5.0.4 @ii mK Ib >
Broken pve-container:amd64 Depends on libpve-guest-common-perl:amd64 < 5.0.4 @ii mR > (>= 5.0.3)
  Considering libpve-guest-common-perl:amd64 101 as a solution to pve-container:amd64 6
  Removing pve-container:amd64 rather than change libpve-guest-common-perl:amd64
Investigating (4) spiceterm:amd64 < 3.3.0 @ii mK Ib >
Broken spiceterm:amd64 Depends on pve-qemu-kvm:amd64 < 8.0.2-5 | 8.0.2-6 @ii umR >
  Considering pve-qemu-kvm:amd64 101 as a solution to spiceterm:amd64 2
  Removing spiceterm:amd64 rather than change pve-qemu-kvm:amd64
Investigating (4) pve-manager:amd64 < 8.0.4 @ii mK Ib >
Broken pve-manager:amd64 Depends on libpve-guest-common-perl:amd64 < 5.0.4 @ii mR > (>= 5.0.2)
  Considering libpve-guest-common-perl:amd64 101 as a solution to pve-manager:amd64 1
  Removing pve-manager:amd64 rather than change libpve-guest-common-perl:amd64
Investigating (4) proxmox-ve:amd64 < 8.0.2 @ii mK Ib >
Broken proxmox-ve:amd64 Depends on pve-manager:amd64 < 8.0.4 @ii mR > (>= 8.0.4)
  Considering pve-manager:amd64 101 as a solution to proxmox-ve:amd64 0
  Removing proxmox-ve:amd64 rather than change pve-manager:amd64
Investigating (5) pve-ha-manager:amd64 < 4.0.2 @ii mK Ib >
Broken pve-ha-manager:amd64 Depends on pve-container:amd64 < 5.0.4 @ii mR > (>= 5.0.1)
  Considering pve-container:amd64 101 as a solution to pve-ha-manager:amd64 9
  Removing pve-ha-manager:amd64 rather than change pve-container:amd64
Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
  libjaeger libjs-sencha-touch libslirp0 liburing2 proxmox-default-kernel proxmox-kernel-helper proxmox-mail-forward
  proxmox-offline-mirror-docs proxmox-offline-mirror-helper
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  ceph-base ceph-common libnfsidmap2 libpve-guest-common-perl libpve-storage-perl libsemanage1 proxmox-ve pve-container
  pve-ha-manager pve-manager pve-qemu-kvm python3-cephfs python3-rados python3-rbd python3-rgw qemu-server spiceterm
The following NEW packages will be installed:
  libevent-core-2.1-7 libnfsidmap1 libprotobuf32 libpython3.11 libpython3.11-minimal libpython3.11-stdlib libsemanage2
  libsepol2 libsubid4 proxmox-kernel-6.2.16-14-pve python3-distutils python3-lib2to3 python3-setuptools python3-systemd
  python3.11 python3.11-minimal
The following packages will be upgraded:
  bind9-dnsutils bind9-host bind9-libs ifupdown2 libldb2 libpython3-stdlib libsemanage-common libsmbclient libtalloc2
  libtevent0 libwbclient0 nfs-common passwd proxmox-kernel-6.2 pve-i18n python3 python3-apt python3-cffi-backend python3-ldb
  python3-markupsafe python3-minimal python3-protobuf python3-pycurl python3-talloc python3-yaml samba-common samba-libs
  smbclient uidmap
29 upgraded, 16 newly installed, 17 to remove and 0 not upgraded.
Need to get 0 B/123 MB of archives.
After this operation, 169 MB of additional disk space will be used.
Do you want to continue? [Y/n]

If I press Y here I still get the:

(pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!
Click to expand...

warning and it exits.

Thanks
 
https://pve.proxmox.com/wiki/Upgrade_from_7_to_8#Failing_upgrade_to_.22bookworm.22

Code: 
W: (pve-apt-hook) You are attempting to remove the meta-package 'proxmox-ve'!


then one or more of the currently existing packages cannot be upgraded since the proper Bookworm repository is not configured.

Check which of the previously used repositories (i.e. for Bullseye) do not exist for Bookworm or have not been upgraded to Bullseye ones.

I'm not sure I fully understand what I'm suggested to do here?

Code: 
root@bla:~ # cat /etc/apt/sources.list
deb http://ftp.debian.org/debian bookworm main contrib
deb http://ftp.debian.org/debian bookworm-updates main contrib
deb http://security.debian.org/debian-security bookworm-security main contrib
deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
# deb http://download.proxmox.com/debian/pve bookworm pvetest
root@bla:~ # ls -l /etc/apt/sources.list.d/
total 4
-rw-r--r-- 1 root root 76 Sep 21  2022 linux.dell.com.sources.list
root@bla:~# cat /etc/apt/sources.list.d/linux.dell.com.sources.list
deb http://linux.dell.com/repo/community/openmanage/10300/focal/ focal main
 
Last edited:
Ok I think I have fixed this as follow:

- for a test in the past I installed ceph. After my fiddling I though I removed it completely but apparently I should not have touched (removed) the /etc/apt/sources.list.d/ceph.list file, which I did.

I fixed my issue as per OP here re-installing the ceph.list file from bookworm + apt update + apt upgrade + apt autoremove
 
Last edited:
You must log in or register to reply here.

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!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

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!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back