Remove node from 2 nodes cluster

[Cyberavis]

Following the documentation

I have found a problem

root@NODE-2:~# pvecm delnode NODE-1
cluster not ready - no quorum?

Using pvecm status I am able to see that the quorum status is listed as "Activity blocked" and is 2.
So you can't remove node from 2 nodes cluster because quorum is 2.

My solution for this is to set the quorum to 1 by

root@NODE-2:~# pvecm expected 1

Might someone tell that is good way to decrease the quorum of cluster or is there a better way?
And should I do something after that, when I want to add another node to this one node cluster (now remaining node have Nodeid 2)?

 

[wolfgang]

Hi,

what Proxmox VE Version you are using?

 

[dale]

Hi, Cyberavis.

I successfully split 2 node cluster online with working vms with simple scripts
executing on both nodes.

~# cat stop.sh
#!/bin/sh
systemctl stop pvestatd.service
systemctl stop pvedaemon.service
systemctl stop pve-cluster.service
systemctl stop corosync
systemctl stop pve-cluster
systemctl stop pve-ha-crm.service
systemctl stop pve-ha-lrm.service

~# cat del.sh
#!/bin/sh
DIR="/var/lib/pve-cluster"
DB="$DIR/config.db"
BIN="sqlite3 -line"
$BIN $DB ".dump" >$DIR/config.db.sql
$BIN $DB "delete from tree where name = 'corosync.conf';"
$BIN $DB "delete from tree where name like 'ha%';"
$BIN $DB "delete from tree where name = 'resources.cfg';"
$BIN $DB "delete from tree where name = 'groups.cfg';"
$BIN $DB "delete from tree where name = 'manager_status';"
$BIN $DB "delete from tree where name = 'crm_commands';"
$BIN $DB "delete from tree where name = 'lock';"
$BIN $DB "delete from tree where name = 'lrm_status';"
pmxcfs -l
rm /etc/pve/corosync.conf
rm /etc/corosync/*
rm /var/lib/corosync/*
find /etc/pve/nodes/* -maxdepth 0 ! -name `hostname` -exec rm -Rf {} \;          

~# cat start.sh
#!/bin/sh
killall pmxcfs
systemctl start pve-cluster
systemctl start corosync
systemctl start pvedaemon.service
systemctl start pvestatd.service
systemctl start pve-ha-crm.service
systemctl start pve-ha-lrm.service

proxmox version 4.X

dale.

 

[Cyberavis]

I try do it in 5.1

root@NODE-2:~# pveversion -v
proxmox-ve: 5.1-25 (running kernel: 4.13.4-1-pve)
pve-manager: 5.1-35 (running version: 5.1-35/722cc488)
pve-kernel-4.13.4-1-pve: 4.13.4-25
libpve-http-server-perl: 2.0-6
lvm2: 2.02.168-pve6
corosync: 2.4.2-pve3
libqb0: 1.0.1-1
pve-cluster: 5.0-15
qemu-server: 5.0-17
pve-firmware: 2.0-3
libpve-common-perl: 5.0-20
libpve-guest-common-perl: 2.0-13
libpve-access-control: 5.0-7
libpve-storage-perl: 5.0-16
pve-libspice-server1: 0.12.8-3
vncterm: 1.5-2
pve-docs: 5.1-12
pve-qemu-kvm: 2.9.1-2
pve-container: 2.0-17
pve-firewall: 3.0-3
pve-ha-manager: 2.0-3
ksm-control-daemon: 1.2-2
glusterfs-client: 3.8.8-1
lxc-pve: 2.1.0-2
lxcfs: 2.0.7-pve4
criu: 2.11.1-1~bpo90
novnc-pve: 0.6-4
smartmontools: 6.5+svn4324-1
zfsutils-linux: 0.7.2-pve1~bpo90

 

[kakao73]

Exactly what I'm looking for!

I try it to 5.2.

But is it safe? No trouble at all until now?