> So to sum up: it is misleading that the output from the ansible task suggests > you to rerun with the --limit option, as it can not be used with > elasticluster?
Yes, exactly. (But there is no way to prevent Ansible from printing that message, AFAIK.) > If a task fails and the cluster is not set up properly, and I do not want to > remove the node, must I fix the ansible task, and then rerun the whole setup > step again? Yes, until the problem causing the failure in the Ansible task is fixed, `elasticluster setup` will continue to fail. > Or is the point of your suggestion above that it is better to remove the > failed node, then fix the ansible scripts, then run setup again on the new > cluster? No: Ansible's playbooks are idempotent, so it's safe to run them over and over again. No need to remove nodes and re-add (unless in the rare cases where the added node is itself the cause of the problem, e.g. because of a wrong or faulty VM image). 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.
