Dear Ana,
> 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
Another workaround is to prepare a customized snapshot and use it with
ElastiCluster:
* start a VM from the official Ubuntu 16.04 image with the OpenStack web
interface;
* log in to the VM and run the following commands (remove indentation):
sudo apt-get update
sudo apt-get install -y python
rm /etc/apt/apt.conf.d/20auto-upgrades
cat > /etc/apt/apt.conf.d/99no-auto-upgrades <<__EOF__
APT::Periodic::Update-Package-Lists "0";
APT::Periodic::Unattended-Upgrade "0";
__EOF__
* save the running VM as a snapshot
* use that snapshot in the ElastiCluster config, in stead of the official image
Hope this helps,
R
--
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.
