Hi Ana, It looks like you are using Vagrant, which does some trickery to setup SSH on your VM. Maybe you can try to use completely different paths for your elasticluster SSH key (not ~/.ssh/id_rsa) just to make sure there is no interference with Vagrant.
Julien 2017-01-16 0:04 GMT+01:00 Ana Jokanović <[email protected]>: > Dear Riccardo, > > I generated new keypair and made sure I set the right path to private and > public key files in the .elasticluster/config. > Still, I am getting the same problem. I attached the fronted log. It seems > there is a problem with cloud-init. > > Also, when I start cluster I do get an error about nodes not being > reachable. > > (elasticluster)vagrant@controller:~$ elasticluster start slurm -n > mycluster > > Starting cluster `mycluster` with 2 compute nodes. > > Starting cluster `mycluster` with 1 frontend nodes. > > (this may take a while...) > > 2017-01-15 21:47:26 controller gc3.elasticluster[5795] *WARNING* > DeprecationWarning: > The novaclient.v2.security_groups module is deprecated and will be removed. > > 2017-01-15 21:47:26 controller gc3.elasticluster[5795] *WARNING* > DeprecationWarning: > The novaclient.v2.images module is deprecated and will be removed after > Nova 15.0.0 is released. Use python-glanceclient or python-openstacksdk > instead. > > 2017-01-15 21:57:50 controller gc3.elasticluster[5795] *ERROR* Some nodes > of the cluster were unreachable within the given 600-seconds timeout: > compute002, compute001, frontend001 > > Configuring the cluster. > > (this too may take a while...) > > Your cluster is ready! > > > Cluster name: mycluster > > Cluster template: slurm > > Default ssh to node: frontend001 > > - compute nodes: 2 > > - frontend nodes: 1 > > > To login on the frontend node, run the command: > > > elasticluster ssh mycluster > > > To upload or download files to the cluster, use the command: > > > elasticluster sftp mycluster > > Best regards, > Ana > > On Sunday, 15 January 2017 16:08:04 UTC+1, Riccardo Murri wrote: >> >> 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. > -- 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.
