You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You would expect the 'TASK [Wait until SSH is available] ' of 'kargo aws --nodes 3 --cluster-name kubbe' to fail too before.
But looking at the comment #37 (comment) it seems there the default ssh_args get overruled in the command line with ''--ssh-extra-args''
CHECKING SSH CONNECTIONS *******************************************************
k8s-mckay-7zw49 | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh.",
"unreachable": true
}
k8s-mckay-1thil | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh.",
"unreachable": true
}
ssh ec2-user@host
root@d05db7b33842:/# ansible -i /root/.kargo/inventory/inventory.cfg -u ec2-user -m ping k8s-mckay-7zw49
k8s-mckay-hrwtl | UNREACHABLE! => {
"changed": false,
"msg": "Failed to connect to the host via ssh.",
"unreachable": true
}
root@d05db7b33842:/# cat > /root/.ansible.cfg
[ssh_connection]
ssh_args=
The text was updated successfully, but these errors were encountered: