Thanks a lot for your in-depth replies!
Maiken

On Tuesday, April 2, 2019 at 11:32:57 AM UTC+2, Maiken Pedersen wrote:
>
> Hi, 
>
> this might be trivial, but when something fails in elasticluster setup 
> step one gets a suggestion to retry with the --limit option
>
> How is this exactly supposed to be applied? See attempt below:
>
> TASK [lmod : Download sources] 
> ********************************************************************************************************************************************************************************************
> 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')],)\",)."}
>     to retry, use: --limit @/home/centos/elasticluster/src/elasticluster/
> share/playbooks/site.retry
>
> PLAY RECAP 
> ****************************************************************************************************************************************************************************************************************
> compute001                 : ok=46   changed=13   unreachable=0    failed=
> 0   
> compute002                 : ok=46   changed=13   unreachable=0    failed=
> 0   
> frontend001                : ok=62   changed=17   unreachable=0    failed=
> 1   
>
> 2019-04-02 11:25:30 elasticluster-final.novalocal gc3.elasticluster[28430] 
> ERROR Command `ansible-playbook 
> --private-key=/home/centos/.ssh/id-rsa-grid 
> /home/centos/elasticluster/src/elasticluster/share/playbooks/site.yml 
> --inventory=/home/centos/.elasticluster/storage/os_verify.inventory 
> --become --become-user=root` failed with exit code 2.
> 2019-04-02 11:25:30 elasticluster-final.novalocal gc3.elasticluster[28430] 
> ERROR Check the output lines above for additional information on this 
> error.
> 2019-04-02 11:25:30 elasticluster-final.novalocal gc3.elasticluster[28430] 
> ERROR The cluster has likely *not* been configured correctly. You may 
> need to re-run `elasticluster setup` or fix the playbooks.
> 2019-04-02 11:25:30 elasticluster-final.novalocal gc3.elasticluster[28430] 
> WARNING Cluster `os_verify` not yet configured. Please, re-run `elasticluster 
> setup os_verify` and/or check your configuration
>
>
>
> (elasticluster)[centos@elasticluster-final ~]$ elasticluster remove-node 
> $clustername compute003  --limit @/home/centos/elasticluster/src/
> elasticluster/share/playbooks/site.retry
> usage: elasticluster [-h] [-v] [-s PATH] [-c PATH] [--version]
>                      
>                      {list-nodes,migrate,stop,setup,list,gc3pie-config,
> sftp,list-templates,start,export,ssh,import,remove-node,resize}
>                      ...
> elasticluster: error: unrecognized arguments: --limit @/home/centos/
> elasticluster/src/elasticluster/share/playbooks/site.retry
>
>
>

-- 
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.

Reply via email to