Issues with 6.17.2-1-pve

S

spleenftw

Member
Oct 6, 2023
75
1
13
Hello,

I recently updated/upgraded via the gui but I got some errors :

root@pivoine:/home/interlope# apt upgrade -y
The following packages were automatically installed and are no longer required:
proxmox-headers-6.14 proxmox-headers-6.14.11-4-pve
Use 'sudo apt autoremove' to remove them.

Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
3 not fully installed or removed.
Space needed: 0 B / 473 GB available

Setting up proxmox-kernel-6.17.2-1-pve-signed (6.17.2-1) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/dkms 6.17.2-1-pve /boot/vmlinuz-6.17.2-1-pve
Sign command: /lib/modules/6.17.2-1-pve/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Autoinstall of module drbd/9.2.15-1 for kernel 6.17.2-1-pve (x86_64)
Building module(s).......(bad exit status: 2)
Failed command:
make -j16 KERNELRELEASE=6.17.2-1-pve -C src/drbd KDIR=/lib/modules/6.17.2-1-pve/build

Error! Bad return status for module build on kernel: 6.17.2-1-pve (x86_64)
Consult /var/lib/dkms/drbd/9.2.15-1/build/make.log for more information.

Autoinstall on 6.17.2-1-pve failed for module(s) drbd(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 1
Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/proxmox-kernel-6.17.2-1-pve-signed.postinst line 20.
dpkg: error processing package proxmox-kernel-6.17.2-1-pve-signed (--configure):
installed proxmox-kernel-6.17.2-1-pve-signed package post-installation script subprocess returned error exit status 2
dpkg: dependency problems prevent configuration of proxmox-kernel-6.17:
proxmox-kernel-6.17 depends on proxmox-kernel-6.17.2-1-pve-signed | proxmox-kernel-6.17.2-1-pve; however:
Package proxmox-kernel-6.17.2-1-pve-signed is not configured yet.
Package proxmox-kernel-6.17.2-1-pve is not installed.
Package proxmox-kernel-6.17.2-1-pve-signed which provides proxmox-kernel-6.17.2-1-pve is not configured yet.

dpkg: error processing package proxmox-kernel-6.17 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of proxmox-default-kernel:
proxmox-default-kernel depends on proxmox-kernel-6.17; however:
Package proxmox-kernel-6.17 is not configured yet.

dpkg: error processing package proxmox-default-kernel (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
proxmox-kernel-6.17.2-1-pve-signed
proxmox-kernel-6.17
proxmox-default-kernel
Error: Sub-process /usr/bin/dpkg returned an error code (1)

Is this simply because of the drdb not working right now with the last kernel ? What can I do ?
 
Last edited:
You are currently using drbd version 9.2.15-1, which is the latest stable version. However, according to the changelog, support for kernel 6.17 has been introduced in version 9.3.0-rc.5.
 
Last edited:
Yes. You can also communicate this to LINBIT, just so that they are aware. However, judging by the release notes, they seem to already be aware of this. You might still want to let them know, just so that they know that there's enough demand to provide 6.17 compatibility quickly.

In the meantime, you will probably want to remove the kernel and the headers for now:
apt remove proxmox-kernel-6.17 proxmox-headers-6.17 proxmox-kernel-6.17.2-1-pve-signed proxmox-headers-6.17.2-1-pve
Click to expand...

While pinning is also a solution, in the meantime you will have the issue that some apt commands will fail due to the DKMS compilation failing. It might thus be easier to remove the kernel and headers in the meantime to avoid this.
 
l.leahu-vladucu said:
Yes. You can also communicate this to LINBIT, just so that they are aware. However, judging by the release notes, they seem to already be aware of this. You might still want to let them know, just so that they know that there's enough demand to provide 6.17 compatibility quickly.

In the meantime, you will probably want to remove the kernel and the headers for now:


While pinning is also a solution, in the meantime you will have the issue that some apt commands will fail due to the DKMS compilation failing. It might thus be easier to remove the kernel and headers in the meantime to avoid this.
Click to expand...
It's already done, it should be out in about a week.

I've tried to remove the kernel and headers but it somehow removes the proxmox-ve packages ?
Code: 
apt remove proxmox-kernel-6.17 proxmox-headers-6.17 proxmox-kernel-6.17.2-1-pve-signed proxmox-headers-6.17.2-1-pve
The following packages were automatically installed and are no longer required:
  proxmox-headers-6.14  proxmox-headers-6.14.11-4-pve
Use 'sudo apt autoremove' to remove them.

REMOVING:
  proxmox-default-headers  proxmox-headers-6.17          proxmox-kernel-6.17                 proxmox-ve
  proxmox-default-kernel   proxmox-headers-6.17.2-1-pve  proxmox-kernel-6.17.2-1-pve-signed

Summary:
  Upgrading: 0, Installing: 0, Removing: 7, Not Upgrading: 0
  3 not fully installed or removed.
  Freed space: 1,094 MB
Continue? [Y/n] ^C
 
spleenftw said:
I've tried to remove the kernel and headers but it somehow removes the proxmox-ve packages ?
Click to expand...
Because it very recently became the new default kernel, thus is not part of the optional dependency chain anymore.
 
  • Like
Reactions: l.leahu-vladucu
l.leahu-vladucu said:
Since Proxmox VE 9.1 is out now, and since kernel 6.17 is the default in PVE 9.1, it might instead make sense to just remove the headers and pin the kernel for now, as explained here. We now also mention the Compatibility issues of LINSTOR/DRBD and kernel 6.17 on our Roadmap for Proxmox VE 9.1.
Click to expand...
Yeah that's what i did, i pinned a 6.14 kernel.

t.lamprecht said:
Because it very recently became the new default kernel, thus is not part of the optional dependency chain anymore.
Click to expand...
Should I still run it ? I'm kinda nervous with the removal of proxmox-ve tho
 
spleenftw said:
Yeah that's what i did, i pinned a 6.14 kernel.


Should I still run it ? I'm kinda nervous with the removal of proxmox-ve tho
Click to expand...
I'd strongly recommend against removing proxmox-ve (it will be blocked by default anyway).
 
You must log in or register to reply here.
Top Bottom