[SOLVED] Downgrade pve-manager

[Sakis]

I am in the process of upgrading-rebooting my 5 cluster nodes.

Unfortunately during upgrading one of them (4th in row), pve-subscription repo errored and it used pve-no-subscription one. I had forgot to comment it. The result is that it has some newer packages and after rebooting this faulty node every 15 or 30 minutes it looses quorum and get disconnected.

faulty node

proxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-40-pve)
pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a)
pve-kernel-2.6.32-40-pve: 2.6.32-160
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-39-pve: 2.6.32-157
pve-kernel-2.6.32-37-pve: 2.6.32-150
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-3
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-11
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

all good nodes

proxmox-ve-2.6.32: 3.4-159 (running kernel: 2.6.32-40-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547)
pve-kernel-2.6.32-40-pve: 2.6.32-159
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-37-pve: 2.6.32-150
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-18
qemu-server: 3.4-6
pve-firmware: 1.1-4
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-33
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.2-10
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

The differences are:

proxmox-ve-2.6.32: 3.4-159 (running kernel: 2.6.32-40-pve) ---> proxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-40-pve)
pve-manager: 3.4-6 (running version: 3.4-6/102d4547) ---> pve-manager: 3.4-9 (running version: 3.4-9/4b51d87a)
fence-agents-pve: 4.0.10-2 ---> fence-agents-pve: 4.0.10-3 (i can ignore it)
pve-qemu-kvm: 2.2-10 ---> pve-qemu-kvm: 2.2-11 (i can ignore it)

So, is it possible to downgrade proxmox-ve and pve-manager??? If yes, how?

 

[wolfgang]

Hi,
you can override the packet manual like this.

 apt-get install pve-manager=3.4-6

 

[Sakis]

Ok so the procedure was like we could do in any other debian package. It worked! I will leave cluster for an hour or two and check stability.

Should i be alerted for this too?
proxmox-ve-2.6.32: 3.4-159 (running kernel: 2.6.32-40-pve) ---> proxmox-ve-2.6.32: 3.4-160 (running kernel: 2.6.32-40-pve)
Would be wise to do also

apt-get install proxmox-ve-2.6.32=3.4-159

or i can wait for enterprise repo to catch up?

Thank you

 

[wolfgang]

This is a meta-packed so you can leave it this way.

 

[Sakis]

Stability problem didn't solved. The package is ok though. I will mark this as Resolved.
Thank you.