Can't upgrade vom 6.x to 7.x because of systemd?

juliusborg

New Member
Jun 22, 2023
2
1
1
Hi there,

i want to go my way to a newer proxmox version finally... but... it doesn't go so well.... after sed replacing buster with bullseye in my sources list files, and do my apt update, i get these outputs if running

apt-get -o Debug::pkgProblemResolver=true dist-upgrade
(grepped for pve)
Code:
Investigating (0) pve-cluster:amd64 < 6.4-1 -> 7.3-3 @ii umU Ib >
Broken pve-cluster:amd64 Depends on systemd:amd64 < 241-7~deb10u9 | 247.3-7+1-pmx11u1 @ii umR >
  Considering systemd:amd64 38 as a solution to pve-cluster:amd64 33
  Removing pve-cluster:amd64 rather than change systemd:amd64
Investigating (0) libpve-access-control:amd64 < 6.4-3 -> 7.4.1 @ii umU Ib >
Broken libpve-access-control:amd64 Depends on pve-cluster:amd64 < 6.4-1 | 7.3-3 @ii umR > (>= 6.1-4)
  Considering pve-cluster:amd64 33 as a solution to libpve-access-control:amd64 21
  Removing libpve-access-control:amd64 rather than change pve-cluster:amd64
Investigating (0) libpve-storage-perl:amd64 < 6.4-1 -> 7.4-3 @ii umU Ib >
Broken libpve-storage-perl:amd64 Depends on pve-cluster:amd64 < 6.4-1 | 7.3-3 @ii umR > (>= 5.0-32)
  Considering pve-cluster:amd64 33 as a solution to libpve-storage-perl:amd64 13
  Removing libpve-storage-perl:amd64 rather than change pve-cluster:amd64
Investigating (0) libpve-guest-common-perl:amd64 < 3.1-5 -> 4.2-4 @ii umU Ib >
Broken libpve-guest-common-perl:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR >
  Considering libpve-access-control:amd64 21 as a solution to libpve-guest-common-perl:amd64 9
  Removing libpve-guest-common-perl:amd64 rather than change libpve-access-control:amd64
Investigating (0) pve-ha-manager:amd64 < 3.1-1 -> 3.6.1 @ii umU Ib >
Broken pve-ha-manager:amd64 Depends on pve-cluster:amd64 < 6.4-1 | 7.3-3 @ii umR > (>= 3.0-17)
  Considering pve-cluster:amd64 33 as a solution to pve-ha-manager:amd64 9
  Removing pve-ha-manager:amd64 rather than change pve-cluster:amd64
Broken librados2-perl:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR >
  Considering libpve-access-control:amd64 21 as a solution to librados2-perl:amd64 7
  Removing librados2-perl:amd64 rather than change libpve-access-control:amd64
Broken qemu-server:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR > (>= 7.2-5)
  Considering libpve-access-control:amd64 21 as a solution to qemu-server:amd64 7
  Removing qemu-server:amd64 rather than change libpve-access-control:amd64
Investigating (0) pve-container:amd64 < 3.3-6 -> 4.4-6 @ii umU Ib >
Broken pve-container:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR > (>= 7.2-5)
  Considering libpve-access-control:amd64 21 as a solution to pve-container:amd64 6
  Removing pve-container:amd64 rather than change libpve-access-control:amd64
Investigating (0) pve-firewall:amd64 < 4.1-4 -> 4.3-4 @ii umU Ib >
Broken pve-firewall:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR >
  Considering libpve-access-control:amd64 21 as a solution to pve-firewall:amd64 6
  Removing pve-firewall:amd64 rather than change libpve-access-control:amd64
Investigating (0) libpve-cluster-api-perl:amd64 < 6.4-1 -> 7.3-3 @ii umU Ib >
Broken libpve-cluster-api-perl:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR >
  Considering libpve-access-control:amd64 21 as a solution to libpve-cluster-api-perl:amd64 2
  Removing libpve-cluster-api-perl:amd64 rather than change libpve-access-control:amd64
Investigating (0) pve-manager:amd64 < 6.4-15 -> 7.4-15 @ii umU Ib >
Broken pve-manager:amd64 Depends on libpve-access-control:amd64 < 6.4-3 | 7.4.1 @ii umR > (>= 7.0-7)
  Considering libpve-access-control:amd64 21 as a solution to pve-manager:amd64 1
  Removing pve-manager:amd64 rather than change libpve-access-control:amd64
Investigating (0) pve-kernel-helper:amd64 < 6.4-20 -> 7.3-8 @ii umU Ib >
Broken pve-kernel-helper:amd64 Depends on systemd:amd64 < 241-7~deb10u9 | 247.3-7+1-pmx11u1 @ii umR >
  Considering systemd:amd64 38 as a solution to pve-kernel-helper:amd64 -1
  Removing pve-kernel-helper:amd64 rather than change systemd:amd64

so for me it looks like systemd is the root cause of my problems, but if i am reading
apt-cache show systemd
right i should be able to statisfy requirements for pve
Code:
Package: systemd
Architecture: amd64
Version: 247.3-7+1-pmx11u1
Multi-Arch: foreign
Priority: important
Section: admin
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Installed-Size: 16028
Pre-Depends: libblkid1 (>= 2.24), libc6 (>= 2.30), libgcrypt20 (>= 1.8.0), liblz4-1 (>= 0.0~r122), liblzma5 (>= 5.1.1alpha+20120614), libselinux1 (>= 3.1~), libzstd1 (>= 1.4.0)
Depends: libacl1 (>= 2.2.23), libapparmor1 (>= 2.13), libaudit1 (>= 1:2.2.1), libcap2 (>= 1:2.24-9~), libcrypt1 (>= 1:4.4.0), libcryptsetup12 (>= 2:2.3), libgnutls30 (>= 3.7.0), libgpg-error0 (>= 1.14), libip4tc2 (>= 1.8.3), libkmod2 (>= 5~), liblz4-1 (>= 0.0~r130), libmount1 (>= 2.30), libpam0g (>= 0.99.7.1), libseccomp2 (>= 2.4.1), libsystemd0 (= 247.3-7+1-pmx11u1), util-linux (>= 2.27.1), mount (>= 2.26), adduser
Recommends: dbus, systemd-timesyncd | time-daemon
Suggests: systemd-container, policykit-1
Conflicts: consolekit, libpam-ck-connector
Breaks: python-dbusmock (<< 0.18), python3-dbusmock (<< 0.18), resolvconf (<< 1.83~), systemd-shim (<< 10-4~), udev (<< 247~)
Filename: dists/bullseye/pve-no-subscription/binary-amd64/systemd_247.3-7+1-pmx11u1_amd64.deb
Size: 4501056
MD5sum: 71b0f0abd6b9cc4f73426255ac6a65c3
SHA256: d8e396d1df27228a8fcb9e040c2fb65084b006a7fdd1d0b5d3fa51e0cc98ce5e
SHA512: e35cb079d6e504f224f407f1efa4b3bf98ca68bfbf9e5c42c4f1e8c2d57e83f3753ed71d678f120b5c8e3f24fbbdefcb9d94d704e2678d12f2d709f0afb33ce9
Homepage: https://www.freedesktop.org/wiki/Software/systemd
Description: system and service manager
Description-md5: 19399579cbc0c47a303288bf15eadcd4

Package: systemd
Version: 247.3-7+deb11u2
Installed-Size: 16028
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Architecture: amd64
Depends: libacl1 (>= 2.2.23), libapparmor1 (>= 2.13), libaudit1 (>= 1:2.2.1), libcap2 (>= 1:2.24-9~), libcrypt1 (>= 1:4.4.0), libcryptsetup12 (>= 2:2.3), libgnutls30 (>= 3.7.0), libgpg-error0 (>= 1.14), libip4tc2 (>= 1.8.3), libkmod2 (>= 5~), liblz4-1 (>= 0.0~r130), libmount1 (>= 2.30), libpam0g (>= 0.99.7.1), libseccomp2 (>= 2.4.1), libsystemd0 (= 247.3-7+deb11u2), util-linux (>= 2.27.1), mount (>= 2.26), adduser
Pre-Depends: libblkid1 (>= 2.24), libc6 (>= 2.30), libgcrypt20 (>= 1.8.0), liblz4-1 (>= 0.0~r122), liblzma5 (>= 5.1.1alpha+20120614), libselinux1 (>= 3.1~), libzstd1 (>= 1.4.0)
Recommends: dbus, systemd-timesyncd | time-daemon
Suggests: systemd-container, policykit-1
Conflicts: consolekit, libpam-ck-connector
Breaks: python-dbusmock (<< 0.18), python3-dbusmock (<< 0.18), resolvconf (<< 1.83~), systemd-shim (<< 10-4~), udev (<< 247~)
Description: system and service manager
Description-md5: 19399579cbc0c47a303288bf15eadcd4
Multi-Arch: foreign
Homepage: https://www.freedesktop.org/wiki/Software/systemd
Tag: admin::boot, implemented-in::c, interface::daemon, role::program,
 works-with::software:running
Section: admin
Priority: important
Filename: pool/main/s/systemd/systemd_247.3-7+deb11u2_amd64.deb
Size: 4501212
MD5sum: 711332c5a4d87a7292d43647ded41ff7
SHA256: bf43313020e668f6f0f9c843748e960b7cc97c81d9126afbd54b0332dca6b575

Package: systemd
Status: install ok installed
Priority: important
Section: admin
Installed-Size: 13519
Maintainer: Debian systemd Maintainers <pkg-systemd-maintainers@lists.alioth.debian.org>
Architecture: amd64
Multi-Arch: foreign
Version: 241-7~deb10u9
Replaces: udev (<< 228-5)
Depends: libacl1 (>= 2.2.23), libapparmor1 (>= 2.9.0-3+exp2), libaudit1 (>= 1:2.2.1), libcap2 (>= 1:2.10), libcryptsetup12 (>= 2:1.6.0), libgnutls30 (>= 3.6.6), libgpg-error0 (>= 1.14), libidn11 (>= 1.13), libip4tc0 (>= 1.6.0+snapshot20161117), libkmod2 (>= 5~), liblz4-1 (>= 0.0~r130), libmount1 (>= 2.30), libpam0g (>= 0.99.7.1), libseccomp2 (>= 2.3.1), libsystemd0 (= 241-7~deb10u9), util-linux (>= 2.27.1), mount (>= 2.26), adduser
Pre-Depends: libblkid1 (>= 2.24), libc6 (>= 2.28), libgcrypt20 (>= 1.8.0), liblz4-1 (>= 0.0~r122), liblzma5 (>= 5.1.1alpha+20120614), libselinux1 (>= 2.1.9)
Recommends: libpam-systemd, dbus
Suggests: systemd-container, policykit-1
Breaks: apparmor (<< 2.9.2-1), ifupdown (<< 0.8.5~), laptop-mode-tools (<< 1.68~), python-dbusmock (<< 0.18), python3-dbusmock (<< 0.18), systemd-shim (<< 10-4~), udev (<< 228-5)
Conflicts: consolekit, libpam-ck-connector
Conffiles:
 /etc/dhcp/dhclient-exit-hooks.d/timesyncd a891f21f45b0648b7082d999bf424591
 /etc/pam.d/systemd-user 3d97692a0125712fcfbd7ddf756f7696
 /etc/systemd/journald.conf f571f0e823d646d7066ddcb32763d674
 /etc/systemd/logind.conf 65afdb550557d875b792b89a67c46016
 /etc/systemd/networkd.conf 1e94f91b9f6cc257b8fca08f89b2e8b1
 /etc/systemd/resolved.conf 0006d0a53b438ce722b06c1bb05c9cae
 /etc/systemd/sleep.conf e912ff7c0833daa5a45d3918b3d6585f
 /etc/systemd/system.conf dbb1fe615344ea000823b6fa70069480
 /etc/systemd/timesyncd.conf e563c788b019216ec2ad3a43bf89e315
 /etc/systemd/user.conf 675370e2d80a4ad957202e68c1b4aaee
Description: system and service manager
 systemd is a system and service manager for Linux. It provides aggressive
 parallelization capabilities, uses socket and D-Bus activation for starting
 services, offers on-demand starting of daemons, keeps track of processes using
 Linux control groups, maintains mount and automount points and implements an
 elaborate transactional dependency-based service control logic.
 .
 systemd is compatible with SysV and LSB init scripts and can work as a
 drop-in replacement for sysvinit.
 .
 Installing the systemd package will not switch your init system unless you
 boot with init=/bin/systemd or install systemd-sysv in addition.
Description-md5: 00afa0c6fd35cc93a91e4654874648cb
Homepage: https://www.freedesktop.org/wiki/Software/systemd


pve6to7 seems to be fine, beside of warnings about upgradeables packages (well i want to migrate from buster to bullseye (and then bookworm))
Code:
pve6to7 --full
= CHECKING VERSION INFORMATION FOR PVE PACKAGES =
Checking for package updates..
WARN: updates for the following packages are available:
(i snipped those out)
Checking proxmox-ve package version..
PASS: proxmox-ve package has version >= 6.4-1
Checking running kernel version..
PASS: expected running kernel '5.4.203-1-pve'.
= CHECKING CLUSTER HEALTH/SETTINGS =
SKIP: standalone node.
= CHECKING HYPER-CONVERGED CEPH STATUS =
SKIP: no hyper-converged ceph setup detected!
= CHECKING CONFIGURED STORAGES =
PASS: storage 'iso-debian' enabled and active.
PASS: storage 'iso-other' enabled and active.
PASS: storage 'iso-software' enabled and active.
PASS: storage 'iso-storage' enabled and active.
PASS: storage 'iso-ubuntu' enabled and active.
PASS: storage 'iso-windows-client' enabled and active.
PASS: storage 'iso-windows-server' enabled and active.
PASS: storage 'local' enabled and active.
PASS: storage 'nodes' enabled and active.
= MISCELLANEOUS CHECKS =
INFO: Checking common daemon services..
PASS: systemd unit 'pveproxy.service' is in state 'active'
PASS: systemd unit 'pvedaemon.service' is in state 'active'
PASS: systemd unit 'pvestatd.service' is in state 'active'
INFO: Checking for running guests..
WARN: 17 running guest(s) detected - consider migrating or stopping them.
INFO: Checking if the local node's hostname 'rb-dev-host' is resolvable..
INFO: Checking if resolved IP is configured on local node..
PASS: Resolved node IP '255.255.255.255' configured and active on single interface.
INFO: Checking backup retention settings..
WARN: storage 'iso-other' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'iso-windows-server' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'nodes' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'iso-storage' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'local' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'iso-debian' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'iso-windows-client' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'iso-ubuntu' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
WARN: storage 'iso-software' - parameter 'maxfiles' is deprecated with PVE 7.x and will be removed in a future version, use 'prune-backups' instead.
INFO: checking CIFS credential location..
PASS: no CIFS credentials at outdated location found.
INFO: Checking custom roles for pool permissions..
INFO: Checking node and guest description/note legnth..
PASS: All node config descriptions fit in the new limit of 64 KiB
PASS: All guest config descriptions fit in the new limit of 8 KiB
INFO: Checking container configs for deprecated lxc.cgroup entries
WARN: The following CTs have 'lxc.cgroup' keys configured, which will be ignored in the new default unified cgroupv2:
    CT 108
    Often it can be enough to change to the new 'lxc.cgroup2' prefix after the upgrade to Proxmox VE 7.x
INFO: Checking storage content type configuration..
PASS: no problems found
INFO: Checking if the suite for the Debian security repository is correct..
PASS: already using 'bullseye-security'
= SUMMARY =
TOTAL:    34
PASSED:   20
SKIPPED:  2
WARNINGS: 12
FAILURES: 0
ATTENTION: Please check the output for detailed information!

there are no pinned packages,
apt-mark showhold

delivers an empty output

so how can i update?
 
Last edited:
Can you provide the output of apt full-upgrade when it asks for confirmation?
I'd like to see the list of upgraded packages and packages that are to be removed. Don't confirm it!

Please provide the output of grep '' /etc/apt/sources.list /etc/apt/sources.list.d/*
 
Aloha,

i figured out that it was a problem where an update to libsystemd0 was messed up by a foreign architecture... after purge removing all forein architecture packages and removing the foreign architecture apt now offers a upgrade without removing pve-.*

I will see tomorrow if it works out :)
 
  • Like
Reactions: mira
Can you provide the output of apt full-upgrade when it asks for confirmation?
I'd like to see the list of upgraded packages and packages that are to be removed. Don't confirm it!

Please provide the output of grep '' /etc/apt/sources.list /etc/apt/sources.list.d/*
I am also suffering the same issue as the OP.

Code:
WARN: The following CTs have 'lxc.cgroup' keys configured, which will be ignored in the new default unified cgroupv2:
    CT 103
    Often it can be enough to change to the new 'lxc.cgroup2' prefix after the upgrade to Proxmox VE 7.x



root@proxmox:/# grep '' /etc/apt/sources.list /etc/apt/sources.list.d/*
Code:
/etc/apt/sources.list:deb http://ftp.au.debian.org/debian bullseye main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://ftp.au.debian.org/debian bullseye-updates main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:# security updates
/etc/apt/sources.list:deb http://security.debian.org bullseye-security main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
/etc/apt/sources.list:
/etc/apt/sources.list.d/pve-enterprise.list:# deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise





root@proxmox:/# apt full-upgrade
Code:
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:
  pve-kernel-5.15.39-1-pve pve-kernel-5.15.39-3-pve pve-kernel-5.15.64-1-pve pve-kernel-5.15.74-1-pve
Use 'apt autoremove' to remove them.
 
I am also suffering the same issue as the OP.

Code:
WARN: The following CTs have 'lxc.cgroup' keys configured, which will be ignored in the new default unified cgroupv2:
    CT 103
    Often it can be enough to change to the new 'lxc.cgroup2' prefix after the upgrade to Proxmox VE 7.x



root@proxmox:/# grep '' /etc/apt/sources.list /etc/apt/sources.list.d/*
Code:
/etc/apt/sources.list:deb http://ftp.au.debian.org/debian bullseye main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://ftp.au.debian.org/debian bullseye-updates main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:# security updates
/etc/apt/sources.list:deb http://security.debian.org bullseye-security main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://download.proxmox.com/debian/pve bullseye pve-no-subscription
/etc/apt/sources.list:
/etc/apt/sources.list.d/pve-enterprise.list:# deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise





root@proxmox:/# apt full-upgrade
Code:
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:
  pve-kernel-5.15.39-1-pve pve-kernel-5.15.39-3-pve pve-kernel-5.15.64-1-pve pve-kernel-5.15.74-1-pve
Use 'apt autoremove' to remove them.
Looks like you're already on the newest PVE 7 (Bullseye) version then?
 
Hi,
Code:
WARN: The following CTs have 'lxc.cgroup' keys configured, which will be ignored in the new default unified cgroupv2:
    CT 103
    Often it can be enough to change to the new 'lxc.cgroup2' prefix after the upgrade to Proxmox VE 7.x
that warning says you have some lxc.cgroup option set in your container configuration /etc/pve/lxc/103.conf. You will need to change that to have the option still apply after the upgrade to Proxmox VE 8.
 

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!

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!