two node max update diverent Kernel

V

vikozo

Renowned Member
May 4, 2014
783
32
93
suisse
www.wombat.ch
Hello

i have to singel Nodes, both all Update

CPU(s) 4 x Intel(R) Core(TM) i5-4570T CPU @ 2.90GHz (1 Socket)
Kernel Version Linux 5.3.10-1-pve #1 SMP PVE 5.3.10-1 (Thu, 14 Nov 2019 10:43:13 +0100)
PVE Manager Version pve-manager/6.1-5/9bf06119

CPU(s) 4 x Intel(R) Core(TM) i3-9100F CPU @ 3.60GHz (1 Socket)
Kernel Version Linux 5.3.13-2-pve #1 SMP PVE 5.3.13-2 (Fri, 24 Jan 2020 09:49:36 +0100)
PVE Manager Version pve-manager/6.1-5/9bf06119

any idea why this is?

have a nice day
vinc
 
yes the source.list is a bit different

pve-04 deb http://ftp.ch.debian.org/debian buster main contrib
pve-04 deb http://ftp.ch.debian.org/debian buster-updates main contrib
pve-04 deb http://security.debian.org buster/updates main contrib
pve-04 deb http://download.proxmox.com/debian/pve buster pve-no-subscription

============================================
srv-03 deb http://ftp.ch.debian.org/debian buster main contrib
srv-03 deb http://security.debian.org/ buster/updates main contrib
srv-03 deb http://download.proxmox.com/debian/pve buster pve-no-subscription
 
hmm -both do have a seemingly correct pve repository entry ..

please post:
* the output of `pveversion -v` on both nodes (to rule out that it's just a missing reboot)
* the output of `apt update` on both nodes
* the output of `apt full-upgrade` on both nodes
 
Hmm?
in order to use a new kernel you need to boot into it!

but if you're reluctant to reboot - please post the complete output of the commands I asked in my above post - then we can potentially find the issue (in case it's not only a missing reboot)
 
yes the reboot did the trick

Linux 5.3.13-3-pve #1 SMP PVE 5.3.13-3 (Fri, 31 Jan 2020 08:17:11 +0100) || pve-manager/6.1-7/13e58d5e
Linux 5.3.13-3-pve #1 SMP PVE 5.3.13-3 (Fri, 31 Jan 2020 08:17:11 +0100) || pve-manager/6.1-7/13e58d5e
 
You must log in or register to reply here.
Top Bottom