Skip to content

Keypair elasticluster is present but has different fingerprint #697

Open

Description

@jrieffel

When trying to start a cluster via openstack, I get the above error.

Keypair elasticluster is present but has different fingerprint

Here's the -vvv

2021-04-03 11:03:09 Johns-MacBook-Pro.local elasticluster[15140] DEBUG Checking keypair elasticluster ...
2021-04-03 11:03:10 Johns-MacBook-Pro.local elasticluster[15140] ERROR Could not start node worker004: Keypair elasticluster is present but has different fingerprint. Aborting! -- <class 'elasticluster.exceptions.KeypairError'>

Could you explain where these keypairs are stored and what they are checked against? The relevant part of my config is below. Changing the user_key_name has no effect, it still checks for keypair elasticluster.

# the `login` section collects information about how to log-in to VMs, including
# SSH key to use for connections
[login/ubuntu]
image_user=ubuntu
image_user_sudo=root
image_sudo=True
# name of SSH key the cloud controller will inject into VMs
#user_key_name=rieffel-laptop-rsa
user_key_name=elasticluster
# these should match the SSH key named above
user_key_private=~/.ssh/id_rsa
user_key_public=~/.ssh/id_rsa.pub

Activity

  1. jrieffel commented on Apr 3, 2021

    @jrieffel
    Author

    Updates:

    • elasticluster is correctly uploading a new key called 'elasticluster' to my openstack account
    • sometimes, one of the keypairs matchines and the instance is created (but elasticluster fails to connect via SSH, but that's a different problem)
  2. jrieffel commented on Apr 3, 2021

    @jrieffel
    Author

    I was able to fix this in a kludgy way by commenting out the lines that throw the exception in openstack.py in the elasticluster code -- and have been able to proceed. But I don't think this is a good long-term solution.

  3. onstring commented on Jul 1, 2021

    @onstring
  4. jrieffel commented on Jul 1, 2021

    @jrieffel
    Author
  5. jeffctr commented on Jul 7, 2021

    @jeffctr

    Having the same issue but, this problem is from paramiko it also was reported issue #1839. Then, I decided to replace paramiko for something more stable so I decide to go with paramiko-ng that is a fork of it. I update the package in the setup.py file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions