Search results

  1. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    More info... On one node of the "broken cluster" I deleted the "known hosts" in the local ssh folder. I then performed a live migration of a vm from one node to this node. It succeeded. I then attempted to live migrate back to the original node and it failed. After restoring the "known hosts"...
  2. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    Still not sure how we got to this state... A bit more info: I can't seem to ssh from most nodes to another without being prompted to accept an SSH key. Comparing to another pve cluster in our environment all nodes can ssh into all nodes with no problem. On the "working" cluster, there is no...
  3. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    Just circling back on this...It's still a problem and I'm having a hard time figuring out how to surgically. I've been limping along for all of this time but I need to add 5 new nodes and I want to make sure this is solved before I do that. Right now, the 5 nodes I have are all in various...
  4. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    So I basically need to pick one of the updated files from /root/.ssh/known_hosts and copy that into the /etc/pve/priv on one of the updated hosts and that should update the rest of the cluster? <D>
  5. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    Also, when you say that if keys are regenerated they must be added and removed....do you mean only to ONE node or to manually to EACH and EVERY node? This would seem to indicate that after a node is joined there isn't any syncronization of known hosts....
  6. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    I'm confirming that those symlinks do exist and the files do appear to be the same but it's not working the way you are explaining it. To be clear, I have not regenerated any keys... When I joined the cluster originally I used: pvecm add IP-ADDRESS-CLUSTER -ring0_addr IP-ADDRESS-RING0 So...
  7. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    So...if I ssh root@<CLUSTERIPOFNEWNODE> once and select YES to add the ECDSA to the list of known hosts I'm able to migrate from this particular existing node to the new node. When I attempted to migrate back it failed.....so I did the same in reverse (allowed the ECDSA key from existing node...
  8. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    Happy to provide this information but I need some clarification....do you want the Syslog from the machine initiating the migration, the syslog from the receiving machine or BOTH? <D>
  9. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    A bit more info.... When I trigger the live migration, the syslog shows the ip address of vmbr0 on the source attempting and SSH session and NOT the dedicated interface or address range... I just confirmed that /etc/pve/datacenter.cfg is configured with the correct range "migration...
  10. D

    BUG / MISSING FEATURE: Host key verification fails after adding node to existing cluster

    All, I've just added a new, 5th node to my existing PVE 4.4-15 cluster and when I attempt to live migrate a VM to the new node it fails with "Host Key Verification Failed". My cluster is configured with a dedicated, separate, network for the cluster communication. All nodes can ping each other...
  11. D

    100% swap usage on machine with 50% free RAM

    swappiness=0 seems to have sorted this out. <D>
  12. D

    How to chage notification email address

    How should one test sending email to make sure it works?
  13. D

    storage is not online 500 after upgrade

    Interesting....This may be related to an issue that I've been chasing for a few days now. I'm using NFS with a cluster of 4 servers. Originally I had the storage configured with one of it's 1G interfaces just to test things before going live. After making sure everything was running fine, I...