v8 upgrade failure "You are attempting to remove the meta-package 'proxmox-ve'"

boomam

Member
Jan 5, 2023
55
10
8
Referencing this post in the announcement thread - https://forum.proxmox.com/threads/proxmox-ve-8-0-released.129320/post-566845
---

Ran upgrade after following the steps in the upgrade guide *to the letter*, got the error that was referenced as being an issue that was caused by installs on Debian directly, instead of via PVE ISOs, ran the upgrade anyway thinking it was a bug...and now both ceph & pve are now wiped from one of my nodes.
Appears that the raw data and config files exist though...

To clarify key points -
  • System was originally a v7.2 iso install.
  • Ceph was already on at least 17.2/Quincy
  • System itself was not modified other than install & config of - Telegraf, Nut, Rsyslog config.
  • No additional kernels were on the system at time of upgrade.
  • pve7to8 tool listed no issues whatsoever.
  • Repo's listed in sources are the ones listed in the install guide.
Attempted re-install of 'proxmox-ve' via apt, yields this error -
Code:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 python3-cephfs : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
 python3-rados : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
 python3-rbd : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
 python3-rgw : Depends: python3 (< 3.10) but 3.11.2-1+b1 is to be installed
E: Unable to correct problems, you have held broken packages.

Any assistance would be appriciated, I'd rather avoid re-setting up Proxmox on this particular node from scratch if i can avoid it.

Thanks!
 
Removing, and replacing the sources.list file (same content) with the content from here, then running 'apt install proxmox-ve', now yields a different error -

Code:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package proxmox-ve is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  pve-kernel-helper proxmox-kernel-helper

E: Package 'proxmox-ve' has no installation candidate
 
Can you provide the output of grep '' /etc/apt/sources.list* /etc/apt/sources.list.d/*?
 
Can you provide the output of grep '' /etc/apt/sources.list* /etc/apt/sources.list.d/*?
Code:
/etc/apt/sources.list:#deb http://ftp.debian.org/debian bookworm main contrib
/etc/apt/sources.list:#deb http://ftp.debian.org/debian bookworm-updates main contrib
/etc/apt/sources.list:#deb http://security.debian.org/debian-security bookworm-security main contrib
/etc/apt/sources.list:#deb http://download.proxmox.com/debian/pve bookworm pve-no-subscription
/etc/apt/sources.list:
/etc/apt/sources.list:deb http://deb.debian.org/debian bookworm main contrib
/etc/apt/sources.list:deb http://deb.debian.org/debian bookworm-updates main contrib
/etc/apt/sources.list:
/etc/apt/sources.list:# security updates
/etc/apt/sources.list:deb http://security.debian.org/debian-security bookworm-security main contrib
grep: /etc/apt/sources.list.d: Is a directory
/etc/apt/sources.list.d/ceph.list:deb http://download.proxmox.com/debian/ceph-quincy bullseye main
/etc/apt/sources.list.d/pve-enterprise.list:# deb https://enterprise.proxmox.com/debian/pve bullseye pve-enterprise
/etc/apt/sources.list.d/pve-enterprise.list:
Interestingly, if i try to install the pve-kernel-helper it tells me its already installed.
If i try to remove it, it tells me its not installed to be able to remove!?
 
/etc/apt/sources.list.d/ceph.list:deb http://download.proxmox.com/debian/ceph-quincy bullseye main

This is most likely the issue. Make sure that ALL repositories are updated to `bookworm`.
 
/etc/apt/sources.list.d/ceph.list:deb http://download.proxmox.com/debian/ceph-quincy bullseye main

This is most likely the issue. Make sure that ALL repositories are updated to `bookworm`.
This does not fix the issue unfortunatelly.
Added, updated apt, apt upgrade, apt install proxmox-ve
Last two steps fail.

Upgrade step -
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:
  ceph-mgr-modules-core g++-10 guile-2.2-libs libfmt7 libfsverity0 libidn11
  libjs-sencha-touch liblua5.2-0 libpython3.9-dev librpm9 librpmbuild9 librpmio9
  librpmsign9 libslirp0 libsqlite3-mod-ceph libstdc++-10-dev libthrift-0.13.0
  libtiff5 libupsclient4 libwebp6 python-babel-localedata python-pastedeploy-tpl
  python-pip-whl python3-asgiref python3-autocommand python3-babel python3-bcrypt
  python3-blinker python3-bs4 python3-cheroot python3-cherrypy3 python3-click
  python3-colorama python3-dateutil python3-dotenv python3-flask python3-inflect
  python3-itsdangerous python3-jaraco.classes python3-jaraco.collections
  python3-jaraco.context python3-jaraco.functools python3-jaraco.text python3-jinja2
  python3-logutils python3-more-itertools python3-natsort python3-netifaces
  python3-paste python3-pastedeploy python3-pastedeploy-tpl python3-pecan
  python3-portend python3-repoze.lru python3-routes python3-rpm
  python3-simplegeneric python3-simplejson python3-singledispatch python3-soupsieve
  python3-tempita python3-tempora python3-tz python3-waitress python3-webob
  python3-webtest python3-werkzeug python3-zc.lockfile python3.9-dev rpm-common
  ruby2.7 sudo telnet
Use 'apt autoremove' to remove them.
The following NEW packages will be installed:
  libfmt9 liblttng-ust-common1 liblttng-ust-ctl5 liblttng-ust1 libthrift-0.17.0
The following packages will be upgraded:
  ceph-fuse ceph-mgr-modules-core libcephfs2 librados2 libradosstriper1 librbd1
  librgw2 libsqlite3-mod-ceph python3-ceph-argparse python3-ceph-common
10 upgraded, 5 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/15.5 MB of archives.
After this operation, 2,369 kB of additional disk space will be used.
/bin/sh: 1: /usr/share/proxmox-ve/pve-apt-hook: not found
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (127)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook

apt install proxmox-ve
Code:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package proxmox-ve is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  pve-kernel-helper proxmox-kernel-helper

E: Package 'proxmox-ve' has no installation candidate

Lastly, i would suggest an update to the install guide if the theory that the root cause is still that repo - it doesn't directly call that out, only says 'At this point a hyper-converged Ceph cluster installed directly in Proxmox VE must run Ceph 17.2 Quincy' -
 
  • Like
Reactions: drvenipatuljak
Uncommenting the pve repos does identify more things to install/upgrade, however still exits out & fails with -
Code:
/bin/sh: 1: /usr/share/proxmox-ve/pve-apt-hook: not found
E: Sub-process /usr/share/proxmox-ve/pve-apt-hook returned an error code (127)
E: Failure running script /usr/share/proxmox-ve/pve-apt-hook
Looking at that location, the hook doesnt exist.
 
Recreating the file (copied the content from another node), with permissions and chmod removes the error, `apt upgrade` ran successfully this time.
`apt install proxmox-ve` is in progress...
 
ok, pve has come up and reconnected to the cluster!
Just ceph to resolve now -
Code:
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 ceph-base : Depends: ceph-common (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
             Recommends: btrfs-tools but it is not installable
             Recommends: ceph-mds (= 16.2.11+ds-2) but it is not going to be installed
             Recommends: librados2 (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
             Recommends: libradosstriper1 (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
             Recommends: librbd1 (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
 ceph-mgr : Depends: ceph-mgr-modules-core (< 16.2.11+ds-2.1~) but 17.2.6-pve1+3 is to be installed
 ceph-osd : PreDepends: ceph-common (= 16.2.11+ds-2) but 17.2.6-pve1+3 is to be installed
            Depends: python3-ceph but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
 
Commenting out the 'enterprise' repo's on the list (as I'm using the non-sub ones) allows Ceph to be reinstalled.
However the OSD will not come back up. I can solve that separately as its likely out of the scope of Proxmox support/forum.

@mira
Can we expect any medium/long-term effect on Proxmox's ability to function following this manual re-install of its components?
Or should it theoretically be fine as the config files remained?
 
Can you provide the repositories again through the previous command?

What's the output of apt full-upgrade when it asks for confirmation?
What's the output of apt -f install?

Please also provide the output of pveversion -v.
 
@mira
Its solved now (scroll up...), I was asking more along the lines of can we expect the re-install causing any potential issues going forward?
 
/etc/apt/sources.list.d/ceph.list:deb http://download.proxmox.com/debian/ceph-quincy bullseye main

This is most likely the issue. Make sure that ALL repositories are updated to `bookworm`.

I had the same problem yesterday. I have never used or installed "ceph". I have been using proxmox since version 6.x. after the installation according to the instructions, I did not have "proxmox-ve".

after editing the "/etc/apt/sources.list.d/ceph.list" list in bookworm I could "apt upgrade", "apt install proxmox-ve" the thing worked.
 
Recreating the file (copied the content from another node), with permissions and chmod removes the error, `apt upgrade` ran successfully this time.
`apt install proxmox-ve` is in progress...
I'm having this same issue. Which file(s) did you copy?
 
in my case - I had Ceph installed but not used (partially installed) so I didn't update the apt source list for it -


I disabled the Proxmox repo - updated the Ceph list - ran the update - and then dist-upgrade - it worked fine - then I enabled the Proxmox repo and another dist-upgrade ran fine



Code:
echo "deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription" > /etc/apt/sources.list.d/ceph.list
apt update
apt upgrade -y
apt dist-upgrade -y

then enabled the Proxmox repo and repeated the last 3 commands.

Hope that helps!
 
Code:
echo "deb http://download.proxmox.com/debian/ceph-quincy bookworm no-subscription" > /etc/apt/sources.list.d/ceph.list
apt update
apt upgrade -y
apt dist-upgrade -y
Please never run apt upgrade with Proxmox, also not as an in-between step and definitely not with "yes to all".
 

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!