proxmox 8 to 9 upgrade

Vorl

Member
Jan 7, 2023
39
2
13
good morning, I updated my test host from 8.3 to 8.4.11 this morning and then upgraded to 9 but it didn't complete the upgrade. Here is what I was able to find on my own.

root@hunsn1:~# apt install --only-upgrade pve-cluster
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:
pve-cluster : Depends: perl (>= 5.40.1-6) but 5.36.0-7+deb12u2 is to be installed
Depends: perlapi-5.40.1 but it is not installable
Depends: libfuse2t64 (>= 2.9.2) but it is not installable
Depends: libglib2.0-0t64 (>= 2.76.0) but it is not installable
Depends: librrd8t64 (>= 1.4~rc2) but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
root@hunsn1:~# apt update
Hit:1 http://download.proxmox.com/debian/pve trixie InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
72 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@hunsn1:~# apt policy
Package files:
100 /var/lib/dpkg/status
release a=now
500 http://download.proxmox.com/debian/pve trixie/pve-no-subscription amd64 Packages
release o=Proxmox,a=stable,n=trixie,l=Proxmox Debian Repository,c=pve-no-subscription,b=amd64
origin download.proxmox.com
Pinned packages:
root@hunsn1:~#


Any thoughts on how I can get this to move forward?

Thanks
 
root@hunsn1:~# apt install --only-upgrade pve-cluster
Where did you find that instruction in the official upgrade guide?
root@hunsn1:~# apt update
Hit:1 http://download.proxmox.com/debian/pve trixie InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
72 packages can be upgraded. Run 'apt list --upgradable' to see them.
Looks like you are missing the Debian repositories. Did you remove them instead of updating them to trixie (like the update guide tells you)? Like older PVE versions, those are also always required:
Code:
Types: deb
URIs: http://ftp.nl.debian.org/debian/
Suites: trixie
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://ftp.nl.debian.org/debian/
Suites: trixie-updates
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

# Modernized from /etc/apt/sources.list
Types: deb
URIs: http://security.debian.org/
Suites: trixie-security
Components: main contrib non-free-firmware
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
And you also need the Ceph repository: https://pve.proxmox.com/wiki/Upgrade_from_8_to_9#Update_the_Ceph_Package_Repository
Any thoughts on how I can get this to move forward?
I would continue here after adding the required repositories: https://pve.proxmox.com/wiki/Upgrad...he_system_to_Debian_Trixie_and_Proxmox_VE_9.0
 
  • Like
Reactions: UdoB
sorry, maybe you should come back after you get your cup of coffee for the morning. While the help is appreciated, the attitude isn't.

I found someone else having an upgrade problem in these forums and it was suggested to use that command to try and find out what was holding things back.

Yes, I read the documentation and followed the steps in upgrading from 8 to 9.

cat > /etc/apt/sources.list.d/proxmox.sources << EOF
Types: deb
URIs: http://download.proxmox.com/debian/pve
Suites: trixie
Components: pve-no-subscription
Signed-By: /usr/share/keyrings/proxmox-archive-keyring.gpg
EOF

As with the enterprise repository, make sure that apt picks it up correctly with apt update followed by apt policy. Then remove the previous Proxmox VE 8 no-subscription repository from either the /etc/apt/sources.list, /etc/apt/sources-list.d/pve-install-repo.list or any other .list file you may have added it to. Run apt update and apt policy again to be certain that the old repo has been removed.

I did miss the step
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list
sed -i 's/bookworm/trixie/g' /etc/apt/sources.list.d/pve-enterprise.list

so thanks for posting the other repos for me.

For the record, your repos didn't work, I copied /etc/apt/sources.list from another running system and ran the sed commands on them. this is how they should look

cat /etc/apt/sources.list

deb http://ftp.us.debian.org/debian trixie main contrib

deb http://ftp.us.debian.org/debian trixie-updates main contrib

# security updates
deb http://security.debian.org trixie-security main contrib

deb http://download.proxmox.com/debian/pve trixie pve-no-subscription


Also, this is still a very kludgy upgrade process. It would be very simple for them to have a standard upgrade script that takes care of this instead of us having to manually edit crap on each host. Yeah, there's ansible but having a standard install script is just a cleaner and more supportable option. This is the kind of thing that would help businesses. Make upgrades as simple as possible for your users.