Cannot add second not to Separate Cluster Network

[WarwickChapman]

Two servers at cloud host.

Secondary NIC on both servers is connected to a switch.

First server secondary NIC (eth1) is 10.0.0.1
Second server secondary NIC (eth1) is 10.0.0.2

Hosts file on both has entries for each of the two:

...
# Proxmox Cluster Hosts
10.0.0.1 eday-apps-a-node.us.io eday-apps-a-node
10.0.0.2 eday-apps-b-node.us.io eday-apps-b-node
...

Created cluster with on eday-apps-a-node:

pvecm create app-servers -bindnet0_addr 10.0.0.1 -ring0_addr eday-apps-a-node

Attempted to add secondary node from secondary node with:

pvecm add 10.0.0.1 -ring0_addr 10.0.0.2

Fails with:

unable to copy ssh ID: exit code 1

/etc/corosync/corosync.conf on eday-apps-a-node contains:

totem {
  version: 2
  secauth: on
  cluster_name: app-servers
  config_version: 1
  ip_version: ipv4
  interface {
    ringnumber: 0
    bindnetaddr: 10.0.0.1
  }
}

nodelist {
  node {
    ring0_addr: eday-apps-a-node
    name: eday-apps-a
    nodeid: 1
    quorum_votes: 1
  }
}

quorum {
  provider: corosync_votequorum
}

logging {
  to_syslog: yes
  debug: off
}

 

[WarwickChapman]

Do I need to log a ticket?

 

[dcsapak]

did you verify that you can ssh to the other node using the 10.x.x.x ip ?
the error

unable to copy ssh ID: exit code 1

means that we cannot copy the public key to the target server

 

[WarwickChapman]

did you verify that you can ssh to the other node using the 10.x.x.x ip ?
the error means that we cannot copy the public key to the target server

Brilliant!

I has to reinstall the one node after experimenting didn't work out. Would be great if this error or something suggesting it could be relayed to user.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@    WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!     @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
32:xx:ba:db:d6:16:xx:xx:xx:10:f6:f9:67:f8:xx:1d.
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /root/.ssh/known_hosts:1
  remove with: ssh-keygen -f "/root/.ssh/known_hosts" -R 10.0.0.1
ECDSA host key for 10.0.0.1 has changed and you have requested strict checking.
Host key verification failed.