Dear Ana: > (elasticluster)vagrant@controller:~$ ssh -v -i /home/vagrant/.ssh/id_rsa > [email protected] > [...] > debug1: Offering RSA public key: /home/vagrant/.ssh/id_rsa > debug1: Authentications that can continue: publickey > debug1: No more authentication methods to try. > Permission denied (publickey).
This shows that the SSH key file `~/.ssh/id_rsa` is *not* the SSH key file associated with the keypair named `elasticluster` in your OpenStack. You should either find the right key files for keypair `elasticluster`, or create a new keypair and configure ElastiCluster to use the new one. Either way, the files pointed to by ElastiCluster's configuration options `user_key_public` and `user_key_private` should point to the public and private SSH keys corresponding to the OpenStack keypair named by ElastiCluster's config option `user_key_name`. It is also possible (but far less likely) that the VM image or snapshot you're using does not allow SSH as user `ubuntu` but requires e.g. that `root` is used instead. This is however not true for the Ubuntu official images (which require SSH as user `ubuntu`), so I would look into this direction only if you're using a 3rd party VM image and you're certain that the key pair config (as described above) is correct. Hope this helps! Ciao, Riccardo -- Riccardo Murri, Schwerzenbacherstrasse 2, CH-8606 Nänikon, Switzerland -- You received this message because you are subscribed to the Google Groups "elasticluster" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
