what is the most safe recipe to update a "2.1" cluster w/o interrupting services?

[jmbeuken]

Hi,

current version on the 3 nodes :

pve-manager: 2.1-1 (pve-manager/2.1/f9b0f63a)
running kernel: 2.6.32-11-pve
proxmox-ve-2.6.32: 2.0-66
pve-kernel-2.6.32-11-pve: 2.6.32-66
lvm2: 2.02.95-1pve2
clvm: 2.02.95-1pve2
corosync-pve: 1.4.3-1
openais-pve: 1.1.4-2
libqb: 0.10.1-2
redhat-cluster-pve: 3.1.8-3
resource-agents-pve: 3.9.2-3
fence-agents-pve: 3.1.7-2
pve-cluster: 1.0-26
qemu-server: 2.0-39
pve-firmware: 1.0-15
libpve-common-perl: 1.0-27
libpve-access-control: 1.0-21
libpve-storage-perl: 2.0-18
vncterm: 1.0-2
vzctl: 3.0.30-2pve5
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-9
ksm-control-daemon: 1.1-1

no HA, only CT with local storage , a common NFS server for backup

- can I update each node one after another after migrate on-line CT on other node ?
- must I reboot the updated node ?

I have already experienced a big problem of restarting the cluster when upgrading from 2.0 to 2.1 ...

thank you for this great software !

best regards

 

[tom]

I suggest you migrate all CT from one node, update this one and reboot to activate kernel. migrate CT back and test if everything is running. if yes, do the same with the other nodes.

in some cases live migrations does not work between different kernels. in this case, do an offline migration or just reboot without moving the CT to another node.

 

[jmbeuken]

Thanks Tom,

I suggest you migrate all CT from one node, update this one and reboot to activate kernel. migrate CT back and test if everything is running. if yes, do the same with the other nodes.

in some cases live migrations does not work between different kernels. in this case, do an offline migration or just reboot without moving the CT to another node.

it works !

obviously, live migrations work with theses two differents kernels ( 2.6.32-11-pve vs 2.6.32-13-pve ) !

ouf ! cluster updated for some months...

PS : I remark that the process "ntpd" prevents online migration : ressource busy...
( stopping ntpd before migration resolves the problem...)

thanks again...

 

[tom]

don´t run ntpd inside a container. not needed.