Hello Maiken,
> fatal: [frontend001]: FAILED! => {"changed": false, "failed": true, "msg":
> "Failed to validate the SSL certificate for github.com:443. Make sure your
> managed systems have a valid CA certificate installed. You can use
> validate_certs=False if you do not need to confirm the servers identity but
> this is unsafe and not recommended. Paths checked for this platform:
> /etc/ssl/certs, /etc/pki/ca-trust/extracted/pem, /etc/pki/tls/certs,
> /usr/share/ca-certificates/cacert.org, /etc/ansible. The exception msg was:
> (\"bad handshake: Error([('SSL routines', 'ssl3_read_bytes', 'tlsv1 alert
> protocol version')],)\",)."}
> 1) How to solve the error above?
Well, to me this looks like an SSL error; it can either be transient
(e.g., problem on GitHub's side -- just retry later), or could be
permanent in which case it would indicate that on your VM the trusted
certificate storage is too old. Are you deploying on CentOS6?
> 2) When resizing the cluster, is it usual to run with --no-setup? What is the
> recommended way?
No, `--no-setup` is just a trick to execute multiple resize/remove
operations without paying the price of a full cluster reconfig each
time. You still have to execute `elasticluster setup` at the end.
See the other email thread on `--limit` for more explanation and an
example.
> 3) I need to run a custom after script and have been doing:
> elasticluster -v setup $clustername --
> $elasticluster_home/elasticluster/src/elasticluster/share/playbooks/after_openstack_arc6.yml
> Can I run this on the new compute only? Like so:
> elasticluster -v setup $clustername --
> $elasticluster_home/elasticluster/src/elasticluster/share/playbooks/after_openstack_arc6.yml
> --limit=compute003
Nope, see email thread on `--limit`.
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.
