Proxmox 8.2.2 - Qdevice

[ihoogen]

Thank you for the info about the patch.
Is there a tutorial for relative noobs how to apply this patch?

Best regards!

Edit: Let me google that for myself

https://forum.proxmox.com/threads/how-to-apply-promox-patch.53657/

It's very simple, download the patch file, install the patch "app" via apt (apt install patch), make a copy of the orignal file (/usr/share/perl5/PVE/CLI/pvecm.pm) and patch the file with patch <file-to-patch> <patch> thats it.

Good Luck.

Best regards.

 

[VictorSTS]

Aaron just posted on bugzilla that the patch has been accepted and will be available on package pve-cluster 8.0.6 [1]

[1] https://bugzilla.proxmox.com/show_bug.cgi?id=5461#c3

 

[aaron]

Aaron just posted on bugzilla that the patch has been accepted and will be available on package pve-cluster 8.0.6 [1]

[1] https://bugzilla.proxmox.com/show_bug.cgi?id=5461#c3

newer than that

8.0.6 as that is the latest one out there, so the next one packaged will include the fix

 

[VictorSTS]

True!
I'm eagerly awaiting the official patched package and typed too fast!

 

[Sejl]

I can confirm it is working on my end!
Thank you everyone!!!

Best regards

 

[ikrsdo]

This does work in 8.2.2



This actually works for me too in Proxmox 8.2.2. I may have missed an ssh connection on my first attempt. Below are the commands I used. This assumes that you've enabled root login on your Qdevice, which is a requirement. When done, use the pvecm status command to verify all the quorum votes are available to the cluster.

Example:

First, on the Qdevice edit /etc/ssh/sshd_config adding PermitRootLogin yes to the config file. Save and close the file. Reboot or restart sshd, using systemctl restart sshd.

Next, create a 2 node cluster using pve1 and pve2.

Finally, install the qdevice software, then ssh and login as root between all your devices and run pvecm qdevice setup from one of your Proxmox nodes, like so....

Qdevice (debian Linux):
apt install corosync-qdevice corosync-qnetd
ssh root@<pve1 IP>
ssh root@<pve2 IP>

Proxmox pve1:
apt install corosync-qdevice
ssh root@<pve2 IP>
ssh root@<qdevice IP>

Proxmox pve2:
apt install corosync-qdevice
ssh root@<pve1 IP>
ssh root@<qdevice IP>
pvecm qdevice setup <qdevice IP> -f
pvecm status

Good luck everyone.

This method works for me.

Thanks.

 

[carles89]

Hi,

No matter how I try, the SSH workaround does not work for me. PVE freshly installed from 8.2 ISO.
I see pve-cluster 8.0.7 is not in the enterprise repos yet, is there any ETA?

BTW, I tried to upgrade using pve-no-subcription (where pve-cluster 8.0.7 has been released) and it asks to remove proxmox-ve and pve-manager. Checked on two different clusters, seems to be a bug:

root@pve-lab:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  proxmox-firewall
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  proxmox-ve pve-manager
The following NEW packages will be installed:
  proxmox-kernel-6.8.8-1-pve-signed
The following packages have been kept back:
  pve-container
The following packages will be upgraded:
  less libarchive13 libc-bin libc-l10n libc6 libglib2.0-0 libgstreamer-plugins-base1.0-0 libnvpair3linux libopeniscsiusr libproxmox-acme-perl
  libproxmox-acme-plugins libpve-cluster-api-perl libpve-cluster-perl libpve-guest-common-perl libpve-notify-perl libpve-rs-perl libpve-storage-perl
  libuutil3linux libzfs4linux libzpool5linux locales open-iscsi proxmox-backup-client proxmox-backup-file-restore proxmox-firewall proxmox-kernel-6.8
  proxmox-widget-toolkit pve-cluster pve-docs pve-esxi-import-tools pve-firewall pve-firmware pve-ha-manager pve-qemu-kvm shim-helpers-amd64-signed
  shim-signed shim-signed-common shim-unsigned spl zabbix-agent zfs-initramfs zfs-zed zfsutils-linux
43 upgraded, 1 newly installed, 2 to remove and 1 not upgraded.
Need to get 307 MB of archives.
After this operation, 580 MB of additional disk space will be used.

root@pve-lab:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following package was automatically installed and is no longer required:
  proxmox-firewall
Use 'apt autoremove' to remove it.
The following packages will be REMOVED:
  proxmox-ve pve-manager
The following NEW packages will be installed:
  proxmox-kernel-6.8.8-1-pve-signed
The following packages have been kept back:
  pve-container
The following packages will be upgraded:
  less libarchive13 libc-bin libc-l10n libc6 libglib2.0-0 libgstreamer-plugins-base1.0-0 libnvpair3linux libopeniscsiusr libproxmox-acme-perl
  libproxmox-acme-plugins libpve-cluster-api-perl libpve-cluster-perl libpve-guest-common-perl libpve-notify-perl libpve-rs-perl libpve-storage-perl
  libuutil3linux libzfs4linux libzpool5linux locales open-iscsi proxmox-backup-client proxmox-backup-file-restore proxmox-firewall proxmox-kernel-6.8
  proxmox-widget-toolkit pve-cluster pve-docs pve-esxi-import-tools pve-firewall pve-firmware pve-ha-manager pve-qemu-kvm shim-helpers-amd64-signed
  shim-signed shim-signed-common shim-unsigned spl zabbix-agent zfs-initramfs zfs-zed zfsutils-linux
43 upgraded, 1 newly installed, 2 to remove and 1 not upgraded.
Need to get 307 MB of archives.
After this operation, 580 MB of additional disk space will be used.

Thank you

 

[carles89]

I answer myself, one of the nodes wasn't unable to verify the authenticity of the other one. I followed this solution:

https://forum.proxmox.com/threads/failed-setup-of-external-quorum.147515/

On first node:
ssh-keyscan second_node_ip >> ~/.ssh/known_hosts

I see more posts about the update issue, so I'm not the only one