[SOLVED] Cluster nodes are up to date but do not use same kernel version

Damien_vo

New Member
Oct 10, 2018
2
0
1
France
Hello :)

I think, the title is straightforward.

I have just done an update on four cluster nodes, they all are up to date but the running kernels are not the same.

Code:
node1:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.17-1-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.17-1-pve: 4.15.17-9

node2:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-11-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.17-1-pve: 4.15.17-9

node3:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.18-9-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.17-1-pve: 4.15.17-9

node4:~# pveversion -v
proxmox-ve: 5.4-1 (running kernel: 4.15.17-1-pve)
pve-manager: 5.4-3 (running version: 5.4-3/0a6eaa62)
pve-kernel-4.15: 5.3-3
pve-kernel-4.15.18-12-pve: 4.15.18-35
pve-kernel-4.15.18-11-pve: 4.15.18-34
pve-kernel-4.15.18-9-pve: 4.15.18-30
pve-kernel-4.15.17-1-pve: 4.15.17-9

I want the nodes to take the last kernel available.
Am I forced to reboot them ?
 
Am I forced to reboot them ?

In general yes, there are some ways of live patching it, but it works not always and mostly provided by external services, not us.
Normally, you free up a node (migrate all important VMs and CTs away to another one) and then reboot it, do this for all nodes in a cluster and you can achieve a downtime-free kernel upgrade (at least with VMs).
 
  • Like
Reactions: Damien_vo