Dear Ana:
> Yes, I did stop the cluster and started new one.
Hmmm... then going back to the error message you posted last, I see two
distinct issues:
1. SSH keys mismatch (not a fatal error)::
fatal: [compute001]: FAILED! => {... "module_stderr": "
... WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED!
... Offending ECDSA key in /home/ajokanovic/.ssh/known_hosts:1
..." ...}
This means that you are connecting to a new VM, but it has taken the
same IP address of an old one. If IP addresses get recycled so quickly
on your OpenStack infrastructure, you might want to avoid that SSH saves
VM host keys to its `~/.ssh/known_hosts` file. The following lines in
`~/.ssh/config` would do the trick (replace `172.16.*.*` with the
appropriate pattern for your OpenStack network)::
Host 172.16.*.*
UserKnownHostsFile /dev/null
2. Python2 is missing::
fatal: [frontend001]: FAILED! => {... /bin/sh: 1: /usr/bin/python: not
found ...}
I have tried with the image URL you posted in one of the last emails.
Indeed, there is apparently a race condition: the `image_userdata`
script is executed *concurrently* with other tasks in the init process.
In particular, it is possible that the SSH server is ready to serve
connections before `image_userdata` has run. In my tests on the local
OpenStack infrastructure, this happens 50% of the time.
If this is the issue, a workaround is the following:
* Start the cluster skipping the setup (Ansible) part::
elasticluster start mycluster
* Wait some time then run the setup::
sleep 30
elasticluster setup mycluster
Adjust the wait time to your local infrastructure: it should be long
enough so that you see the "Cloud-init v. 0.7.8 finished" message in the
VM boot log.
> Now, I am running ElastiCluster on an OpenStack cluster, but it seems I
> should restrict execution of ElastiCluster to a couple of nodes that are
> well configured.
>
> Is there a way to tell ElastiCluster on which nodes to deploy the VMs?
No, the OpenStack API (nor the APIs of any cloud provider, as far as I
know) do not allow giving such hints to the VM placement scheduler.
Ciao,
R
--
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.
