iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Merge pull request #5322 from danielcompton/patch-1 

Add troubleshooting steps to Ansible provisioner docs
This commit is contained in:
Matthew Hooker 2017-09-11 11:43:32 -07:00 committed by GitHub
parent bdd8ff104d b754862fd8
commit 9977edc4b4
1 changed files with 24 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
website/source/docs/provisioners/ansible.html.md
View File

@ -136,6 +136,16 @@ commonly useful Ansible variables:
machine that the script is running on. This is useful if you want to run
only certain parts of the playbook on systems built with certain builders.
## Debugging
To debug underlying issues with Ansible, add `"-vvvv"` to `"extra_arguments"` to enable verbose logging.
``` json
{
"extra_arguments": [ "-vvvv" ]
}
```
## Limitations
### Redhat / CentOS
@ -231,3 +241,17 @@ This template should build a Windows Server 2012 image on Google Cloud Platform:
]
}
```
### Too many SSH keys
SSH servers only allow you to attempt to authenticate a certain number of times. All of your loaded keys will be tried before the dynamically generated key. If you have too many SSH keys loaded in your `ssh-agent`, the Ansible provisioner may fail authentication with a message similar to this:
```console
googlecompute: fatal: [default]: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh: Warning: Permanently added '[127.0.0.1]:62684' (RSA) to the list of known hosts.\r\nReceived disconnect from 127.0.0.1 port 62684:2: too many authentication failures\r\nAuthentication failed.\r\n", "unreachable": true}
```
To unload all keys from your `ssh-agent`, run:
```console
$ ssh-add -D
```