pve-qemu-kvm has been kept back

ikogan

Well-Known Member
Apr 8, 2017
37
2
48
39
Hi,

I just did a test upgrade from 4.4 to 5.1 on a freshly installed test VM after it has been configured to match my production hosts. The upgrade had a few minor issues that needed to be solved but I'm hitting one that I'm not sure how to deal with.

It seems that apt wants to keep the pve-qemu-kvm package back which I can only imagine is going to cause a ton of havoc. Since this is running in a VM, I haven't actually tried to create any VMs as I don't know if my system supports nested virtualization. Here's some information about the system:

Code:
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.13.4-1-pve: 4.13.4-25
pve-kernel-4.4.35-1-pve: 4.4.35-77
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.0-5~pve4
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90
ceph: 12.2.1-1~bpo80+1

Code:
 pve-test# sudo 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:
  pve-qemu-kvm
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.

Code:
pve-test# sudo apt-get install pve-qemu-kvm
Reading package lists... Done
Building dependency tree
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-qemu-kvm : Depends: libsnappy1v5 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

Code:
pve-test# sudo apt-get install libsnappy1v5
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  fonts-font-awesome libappconfig-perl libbabeltrace-ctf1 libbabeltrace1 libdw1 libelf1 libiscsi7 libjs-extjs libjs-mochikit libpve-guest-common-perl libpve-http-server-perl libradosstriper1 libtemplate-perl python-cherrypy3 python-cssselect python-formencode python-logutils python-mako python-openid python-paste
  python-pastedeploy python-pastedeploy-tpl python-pastescript python-pecan python-prettytable python-pyquery python-repoze.lru python-routes python-scgi python-simplegeneric python-tempita python-waitress python-webob python-webtest
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  ceph ceph-base ceph-common ceph-mgr ceph-mon ceph-osd libleveldb1 libsnappy1 proxmox-ve pve-container pve-ha-manager pve-manager pve-qemu-kvm qemu-server spiceterm
The following NEW packages will be installed:
  libsnappy1v5
0 upgraded, 1 newly installed, 15 to remove and 0 not upgraded.
Need to get 51.0 kB of archives.
After this operation, 323 MB disk space will be freed.
Do you want to continue? [Y/n]

One particular weirdness about my setup is that I have a FreeIPA Client installed. Prior to this upgrade, I was using numeezy's jessie repository. There doesn't seem to be one for stretch so I decided to see what would happen if I used the jessie repository. I expected it might cause an issue but the PVE packages aren't where I expected it to be. Is there a good way to know what the culprit might be?
 
you cannot install PVE 5.x on top of Debian Jessie..
 
Ah hah, while I wasn't doing that originally, in responding to your comment I noticed that I forgot to switch ceph's repo to stretch. Whoops. That fixed the issue.
 
I'm confronting the same issue, but my repos are set to stretch.
Code:
root@jfr-pve-01:~# apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease                                         
Hit:2 http://download.proxmox.com/debian/ceph-luminous stretch InRelease                                               
Hit:3 http://download.proxmox.com/debian stretch InRelease                               
Ign:4 http://ftp.debian.org/debian stretch InRelease               
Hit:5 http://ftp.debian.org/debian stretch Release
Reading package lists... Done
root@jfr-pve-01:~# 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:
  pve-qemu-kvm
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
root@jfr-pve-01:~#

Package Details:
Code:
proxmox-ve: 5.1-28 (running kernel: 4.13.8-2-pve)
pve-manager: 5.1-36 (running version: 5.1-36/131401db)
pve-kernel-4.4.35-2-pve: 4.4.35-79
pve-kernel-4.4.83-1-pve: 4.4.83-96
pve-kernel-4.4.76-1-pve: 4.4.76-94
pve-kernel-4.4.62-1-pve: 4.4.62-88
pve-kernel-4.13.8-2-pve: 4.13.8-28
pve-kernel-4.4.35-1-pve: 4.4.35-77
pve-kernel-4.4.95-1-pve: 4.4.95-99
pve-kernel-4.4.79-1-pve: 4.4.79-95
pve-kernel-4.4.67-1-pve: 4.4.67-92
pve-kernel-4.4.59-1-pve: 4.4.59-87
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2~pve4
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.3-pve1~bpo9
openvswitch-switch: 2.7.0-2
ceph: 12.2.2-1~bpo80+1

Any suggestions?
 
12.2.2-1~bpo80+1

you have upstream ceph packages for Debian Jessie installed even if you no longer have the upstream repository configured.
 
there is always a small window directly after an upstream release where upgrading from 4 to 5 puts you into this situation, because we haven't released Ceph packages for the new upstream release (12.2.2 in this case) yet. you can either upgrade to upstreams Stretch packages before switching to our Ceph repository, or wait a few days until our repository contains the updated packages. this is a one-time issue when upgrading from 4 to 5..
 
there is always a small window directly after an upstream release where upgrading from 4 to 5 puts you into this situation, because we haven't released Ceph packages for the new upstream release (12.2.2 in this case) yet. you can either upgrade to upstreams Stretch packages before switching to our Ceph repository, or wait a few days until our repository contains the updated packages. this is a one-time issue when upgrading from 4 to 5..

Understood:). I will wait until the repos are updated;).

Thanks for your Guidance!
 

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!