clean new install: add node: authentication key already exists

[pxo]

Hello,

i clean install jessie, proxmox ve via wiki articles:
i can create new cluster name, when i add the node2 then i becomes this error:

authentication key already exists

the 2 machines clean install !?
this the firsts pve commands that tiped:

root@pve1 ~ > pvecm create 11
Corosync Cluster Engine Authentication key generator.
Gathering 1024 bits for key from /dev/urandom.
Writing corosync key to /etc/corosync/authkey.
root@pve1 ~ > pvecm status
Quorum information
------------------
Date:  Wed Feb  3 17:23:38 2016
Quorum provider:  corosync_votequorum
Nodes:  1
Node ID:  0x00000001
Ring ID:  4
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.0.151 (local)
root@pve1 ~ > pvecm add 10.1.0.152
authentication key already exists
root@pve1 ~ > pvecm nodes

Membership information
----------------------
  Nodeid  Votes Name
  1  1 pve1 (local)
root@pve1 ~ >

I die Installation A Second times completely new beginning , same result

 

[pxo]

Sorry my mistake , who can read ... I have tried from node1

 

[PMoxSudo]

I got the same message when I tried to:

testcluster:
pve1
pve2

create cluster on pve1
add pve2 from pve1

you need to add pve1 from inside pve2.

See https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster, but it's rather confusing.

as root on pve1:

pvecm create YOUR-CLUSTER-NAME

pvecm status

as root on pve2:

pvecm add pve1.hostnameo or pve1's ip

Read this https://pve.proxmox.com/wiki/Troubleshooting_multicast,_quorum_and_cluster_issues and https://forum.proxmox.com/threads/2-0-rc1-authentication-key-already-exists.8503/#post-48020.

On https://pve.proxmox.com/wiki/Proxmox_VE_4.x_Cluster, you're not told you need to join the new cluster from pve2.

You're also not told it happens over ssh and you better copy /root/.ssh/id_rsa.pub from pve2 into pve1's /root/.ssh/authorized_keys.

They need to be on same subnet like on tinc or a test network(like 10.0.60.0/24).