Trouble with cluster creation

ChAoS

Member
Apr 29, 2021
31
4
8
41
Dear Proxmox forum,

I am now struggeling since 1 day with creating a PVE7 cluster.

1st Machine is a Lenovo SR650 already containing (productive) VMs.

4 NICs:
1: connecting to 10.1.20.31 (for proxmox Webinterface, VLAN tagged 20)
2: connecting to 10.1.30.31 (for cluster networking, VLAN tagged 30)
3: for VM traffic untagged
4: NC

I created a cluster in many ways, via gui even via CLI.
For cleaning up use following commands:

systemctl stop pve-cluster
systemctl stop corosync
pmxcfs -l
rm /etc/pve/corosync.conf
rm -r /etc/corosync/*
killall pmxcfs
systemctl start pve-cluster

and remove the ghost with pvecm delnode [name]



I create the cluster with success via:
pvecm create PVE-CL-K-1 -link0 10.1.30.31

no error.

Code:
root@PVE-BKP-K-1:~# pvecm status
Cluster information
-------------------
Name:             PVE-CL-K-1
Config Version:   5
Transport:        knet
Secure auth:      on

Quorum information
------------------
Date:             Tue Jul 20 11:05:55 2021
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1.f2
Quorate:          Yes

Votequorum information
----------------------
Expected votes:   1
Highest expected: 1
Total votes:      1
Quorum:           1
Flags:            Quorate

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 10.1.30.31 (local)
root@PVE-BKP-K-1:~#

Adding the second node:
normal pc

10.1.20.46 comes from switch untagged for webinterface traffic
10.1.30.46 comes tagged

Code:
root@PVE-K-2:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!

auto lo
iface lo inet loopback

iface enx002432181cbc inet manual

iface enp1s0 inet manual

auto vmbr0
iface vmbr0 inet static
        address 10.1.20.46/24
        gateway 10.1.20.254
        bridge-ports enx002432181cbc
        bridge-stp off
        bridge-fd 0

auto vlan30
iface vlan30 inet static
        address 10.1.30.46/24
        vlan-raw-device enx002432181cbc

root@PVE-K-2:~#

nodes can ping each other in both networks.

Code:
root@PVE-K-2:~# pvecm add 10.1.20.31 -link0 10.1.30.46
Please enter superuser (root) password for '10.1.20.31': *******
Establishing API connection with host '10.1.20.31'
The authenticity of host '10.1.20.31' can't be established.
X509 SHA256 key fingerprint is 3xxxFD:2A:B0:5xx3:xx
Are you sure you want to continue connecting (yes/no)? yes
Login succeeded.
check cluster join API version
Request addition of this node
Join request OK, finishing setup locally
stopping pve-cluster service
backup old database to '/var/lib/pve-cluster/backup/config-1626771346.sql.gz'
waiting for quorum...OK

after that the 2nd node hangs and I am getting hung and blocked messages on the local terminal on the 2nd node...

am I blind? did I something wrong?

Both have the same local time, both rebooted... tested many times, even via gui and cli.

Thank you very much

Dirk
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!