Could not verify remote node certificate

[eugalata]

Hi,
I setup 2-node cluster using config from this post: https://forum.proxmox.com/threads/how-to-deploy-a-2-node-cluster-on-proxmox-4-x-ve.33550/

But in web I see

on first node:

root@demo-node1 ~ # pvecm nodes

Membership information
----------------------
    Nodeid      Votes Name
         1          1 demo-node1 (local)

root@demo-node1 ~ # pvecm status
Quorum information
------------------
Date:             Wed Aug  9 18:46:17 2017
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1/24
Quorate:          Yes

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

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 xx.xx.xx.xx (local)

 

[Alwin]

The second node was not added to the cluster. Otherwise it would show up in pvecm status. Try to add it with pvecm add <IP-of-first-node>. I presume that you changed already the corosync.conf, the second node shows up by its own when it was added with pvecm.

 

[eugalata]

I have reinstalled proxmox on node2 and added again:

root@demo-node2 ~ # pvecm add xx.xx.xx.xx
The authenticity of host 'xx.xx.xx.xx (xx.xx.xx.xx)' can't be established.
ECDSA key fingerprint is SHA256:teKrB8Xc99bl9iDTZTG8pSh1KbBGEQZSQ8NXRwZpAx4.
Are you sure you want to continue connecting (yes/no)? yes
root@xx.xx.xx.xx's password:
copy corosync auth key
stopping pve-cluster service
backup old database
waiting for quorum...OK
generating node certificates
merge known_hosts file
restart services
successfully added node 'demo-node2' to cluster.

And I have the same issue

On node1:

root@demo-node1 ~ # pvecm status
Quorum information
------------------
Date:             Thu Aug 10 12:37:17 2017
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000001
Ring ID:          1/24
Quorate:          Yes

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

Membership information
----------------------
    Nodeid      Votes Name
0x00000001          1 xx.xx.xx.xx (local)

on node2:

Quorum information
------------------
Date:             Thu Aug 10 12:38:20 2017
Quorum provider:  corosync_votequorum
Nodes:            1
Node ID:          0x00000002
Ring ID:          2/4
Quorate:          Yes

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

Membership information
----------------------
    Nodeid      Votes Name
0x00000002          1 xx.xx.xx.xx (local)

 

[Alwin]

How does your corosync.conf look like? You changed the default configuration, with the values from the other post? Add the nodes before you do the changes in corosync.conf.

 

[eugalata]

I have reinstalled proxmox on both nodes. corosync.conf is default:

root@demo-node1 ~ # cat /etc/corosync/corosync.conf
logging {
  debug: off
  to_syslog: yes
}

nodelist {
  node {
    name: demo-node2
    nodeid: 2
    quorum_votes: 1
    ring0_addr: demo-node2
  }

  node {
    name: demo-node1
    nodeid: 1
    quorum_votes: 1
    ring0_addr: demo-node1
  }

}

quorum {
  provider: corosync_votequorum
}

totem {
  cluster_name: demo
  config_version: 2
  ip_version: ipv4
  secauth: on
  version: 2
  interface {
    bindnetaddr: xx.xx.xx.xx
    ringnumber: 0
  }

}

But when I try add new node I see:

root@demo-node2 ~ # pvecm add xx.xx.xx.xx
Are you sure you want to continue connecting (yes/no)? tes
Please type 'yes' or 'no': yes
root@xx.xx.xx.xx's password:
copy corosync auth key
stopping pve-cluster service
backup old database
waiting for quorum...

I dont have multicast between nodes

 

[Alwin]

Multicast is necessary for corosync to work. If you cant' use multicast, then you need to configure corosync for udpu, you will find some posts on the forum for this.