diff options
| author | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2014-11-17 12:12:25 +0000 |
|---|---|---|
| committer | Sam Thursfield <sam.thursfield@codethink.co.uk> | 2014-11-17 12:12:25 +0000 |
| commit | bd80ed9a1690accd8d5dcb964ce387a27f6b014b (patch) | |
| tree | 1db72b533e0f2ff7c3661e870388694f683f0c03 /http-assets | |
| parent | 5f2dab59ff6e70edf6ffbcd65fe64b487c4380c2 (diff) | |
| download | trove-setup-bd80ed9a1690accd8d5dcb964ce387a27f6b014b.tar.gz | |
Avoid scanning SSH host key of UPSTREAM_TROVE unless necessarysam/fix-init-behind-proxy
I've seen trove-setup.service fail in the case that the Trove is behind
a proxy that blocks SSH traffic due to `ssh-keyscan` returning an error.
We only need to scan the SSH host key of UPSTREAM_TROVE if we're going
to be using SSH to acess it, so we can work around this issue.
This pulls in the 'sshknownhosts' Ansible module from commit
80f31fa8a5d3751b4e3e19123164c3ea97f262dd of
<https://github.com/bfmartin/ansible-sshknownhosts>. The module seems
small enough that we don't need to mess with a submodules to include it.
Diffstat (limited to 'http-assets')
0 files changed, 0 insertions, 0 deletions