Linux Kernel Version Stuck, Will Not Upgrade

[Mihai]

I've got a 2 node proxmox cluster.

VMHost3:

Kernel Version
Linux 4.2.2-1-pve #1 SMP Mon Oct 5 18:23:31 CEST 2015

PVE Manager Version
pve-manager/4.4-15/7599e35a​

VMHost4:

Kernel Version
Linux 4.4.67-1-pve #1 SMP PVE 4.4.67-92 (Fri, 23 Jun 2017 08:22:06 +0200)

PVE Manager Version
pve-manager/4.4-15/7599e35a​

As you can see VMHost4 has kernel 4.4.57 and VMHost3 is stuck at 4.2.2-1.

There is no option to upgrade the kernel.

I checked both apt lists and they seem identical. I can't post the actual text here because they have URLs and I'm a "new" member and spam reasons... =( I've attached a text file instead

Any ideas how to resolve this?

 

[tom]

any error message on "apt-get update"?

and post the full output of:

> pveversion -v

maybe you just forgot to reboot?

btw, both hosts are outdated.

 

[Mihai]

No error messages on "apt-get update"

Here's the output for pveversion -v

proxmox-ve: not correctly installed (running kernel: 4.2.2-1-pve)
pve-manager: 4.4-15 (running version: 4.4-15/7599e35a)
pve-kernel-4.2.2-1-pve: 4.2.2-16
lvm2: 2.02.116-pve3
corosync-pve: 2.4.2-2~pve4+1
libqb0: 1.0.1-1
pve-cluster: 4.0-52
qemu-server: 4.0-110
pve-firmware: 1.1-11
libpve-common-perl: 4.0-95
libpve-access-control: 4.0-23
libpve-storage-perl: 4.0-76
pve-libspice-server1: 0.12.8-2
vncterm: 1.3-2
pve-docs: 4.4-4
pve-qemu-kvm: 2.7.1-4
pve-container: 1.0-101
pve-firewall: 2.0-33
pve-ha-manager: 1.0-41
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u3
lxc-pve: 2.0.7-4
lxcfs: 2.0.6-pve1
criu: 1.6.0-1
novnc-pve: 0.5-9
smartmontools: 6.5+svn4324-1~pve80
zfsutils: 0.6.5.9-pve15~bpo80
​

Yeah I know we're behind a bit on updates =)


I update all the hosts on the same day. Here are the last reboots:

VMHost3

wtmp begins Tue Aug 1 16:10:00 2017​

VMHost4

wtmp begins Tue Aug 1 16:12:15 2017​

 

[tom]

No error messages on "apt-get update"

Here's the output for pveversion -v

proxmox-ve: not correctly installed (running kernel: 4.2.2-1-pve)
​

Please run:

> apt-get update

> apt-get install proxmox-ve

if this does not fix the issue, please pots the full output of the commands above.

 

[Mihai]

apt-get install proxmox-ve worked and I'm seeing the newest kernel.

Thank you Tom.

 

[Pourya Mehdinejad]

Please run:

> apt-get update

> apt-get install proxmox-ve

if this does not fix the issue, please pots the full output of the commands above.

I'm having the same issue, while my other nodes are:
Linux 4.15.18-20-pve #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200)

One of the nodes stuck on :
Linux 4.15.18-9-pve #1 SMP PVE 4.15.18-30 (Thu, 15 Nov 2018 13:32:46 +0100)

repositories are the same.

apt update && apt upgrade & apt install proxmox-ve doesn't do anything as they say there is no update available.
Would appreciate your help

 

[Pourya Mehdinejad]

I'm having the same issue, while my other nodes are:
Linux 4.15.18-20-pve #1 SMP PVE 4.15.18-46 (Thu, 8 Aug 2019 10:42:06 +0200)

One of the nodes stuck on :
Linux 4.15.18-9-pve #1 SMP PVE 4.15.18-30 (Thu, 15 Nov 2018 13:32:46 +0100)

repositories are the same.

apt update && apt upgrade & apt install proxmox-ve doesn't do anything as they say there is no update available.
Would appreciate your help

Actually when I go to /boot I can see two new kernels are there:

vmlinuz-4.15.18-20-pve
vmlinuz-4.15.18-21-pve

But for some reason, the node is still booting from the older kernel.

 

[oguz]

hi,

But for some reason, the node is still booting from the older kernel.

maybe your grub config in /boot/grub/grub.cfg isn't updated for some reason?

maybe try reinstalling grub, or regenerate the config?

 

[Pourya Mehdinejad]

hi,


maybe your grub config in /boot/grub/grub.cfg isn't updated for some reason?

maybe try reinstalling grub, or regenerate the config?

Updating grub didn't make a difference.
I will try to reinstall it as well.
I realized this issue happened only in two of my nodes, which are using ZFS drives for boot. Could this be related?