Ansible: ssh-extra-args ProxyCommand menonaktifkan host_key_checking=False

Dibuat pada 11 Mar 2016  ·  3Komentar  ·  Sumber: ansible/ansible

Jenis Masalah:
  • Laporan Bug
    Versi yang Mungkin:
ansible 2.0.1.0
  config file = /Users/tpai/src/cm/ansible.cfg
  configured module search path = Default w/o overrides
Konfigurasi yang Mungkin:
[defaults]

host_key_checking=False
timeout=20
forks=20

force_handlers = True
roles_path = ./roles
callback_whitelist=profile_tasks
filter_plugins = ./filter_plugins

[ssh_connection]
pipelining = True
control_path = /tmp/ansible-ssh-%%h-%%p-%%r
Lingkungan:

Host yang memungkinkan : OS X 10.11.3
Target : Ubuntu 14.04.02

Ringkasan:

ssh-extra-args ProxyCommand rusak host_key_checking=False .

Saat menggunakan ssh-extra-args dengan host_key_checking=False diatur di ansible.cfg atau di ssh-extra-args itu sendiri, saya masih diminta untuk menerima kunci untuk Host yang belum saya sambungkan untuk sebelumnya.

Langkah-langkah Untuk Mereproduksi:
ansible-playbook provision_envs/configure-sid.yml -i inventory/sid --limit=tag_build_5 --vault-password-file ../vault_key --ssh-extra-args='-o ProxyCommand="ssh -W %h:%p [email protected]"' -vvvvv
Hasil yang diharapkan:

Menjalankan playbook melawan host baru.

Hasil nyata:

Anda diminta untuk menerima kunci seolah-olah StrictHostKeyChecking telah diaktifkan.

$ ansible-playbook provision_envs/configure-sid.yml -i inventory/sid --limit=tag_build_5 --vault-password-file ../vault_key --ssh-extra-args='-o ProxyCommand="ssh -W %h:%p [email protected]"' -vvvvv
Using /Users/tpai/src/cm/ansible.cfg as config file
Loaded callback default of type stdout, v2.0
Loaded callback profile_tasks of type aggregate, v2.0
2 plays in provision_envs/configure-sid.yml

PLAY ***************************************************************************
skipping: no hosts matched

PLAY ***************************************************************************

TASK [setup] *******************************************************************
Friday 11 March 2016  12:40:12 +0000 (0:00:00.122)       0:00:00.122 **********
<10.0.251.222> ESTABLISH SSH CONNECTION FOR USER: user
<10.0.251.222> SSH: ansible.cfg set ssh_args: (-o)(ControlMaster=auto)(-o)(ControlPersist=60s)
<10.0.251.222> SSH: ANSIBLE_HOST_KEY_CHECKING/host_key_checking disabled: (-o)(StrictHostKeyChecking=no)
<10.0.251.222> SSH: ansible_password/ansible_ssh_pass not set: (-o)(KbdInteractiveAuthentication=no)(-o)(PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey)(-o)(PasswordAuthentication=no)
<10.0.251.222> SSH: ANSIBLE_REMOTE_USER/remote_user/ansible_user/user/-u set: (-o)(User=user)
<10.0.251.222> SSH: ANSIBLE_TIMEOUT/timeout set: (-o)(ConnectTimeout=20)
<10.0.251.222> SSH: PlayContext set ssh_common_args: ()
<10.0.251.222> SSH: PlayContext set ssh_extra_args: (-o)(ProxyCommand=ssh -W %h:%p [email protected])
<10.0.251.222> SSH: found only ControlPersist; added ControlPath: (-o)(ControlPath=/tmp/ansible-ssh-%h-%p-%r)
<10.0.251.222> SSH: EXEC ssh -C -vvv -o ControlMaster=auto -o ControlPersist=60s -o StrictHostKeyChecking=no -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o User=user -o ConnectTimeout=20 -o 'ProxyCommand=ssh -W %h:%p [email protected]' -o ControlPath=/tmp/ansible-ssh-%h-%p-%r 10.0.251.222 '/bin/sh -c '"'"'LANG=en_GB.UTF-8 LC_ALL=en_GB.UTF-8 LC_MESSAGES=en_GB.UTF-8 /usr/bin/python'"'"''
The authenticity of host 'host.com (1.2.3.4)' can't be established.
ECDSA key fingerprint is SHA256:kjghdfjkghdkfjghkdjfgdfgdfjghdkjfg.
Are you sure you want to continue connecting (yes/no)? 

**ssh connection times out**

fatal: [7.8.9.0]: UNREACHABLE! => {"changed": false, "msg": "SSH Error: data could not be sent to the remote host. Make sure this host can be reached over ssh", "unreachable": true}
        to retry, use: --limit @provision_envs/configure-sid.retry

PLAY RECAP *********************************************************************
7.8.9.0               : ok=0    changed=0    unreachable=1    failed=0

Komentar yang paling membantu

Ini bukan bug. Anda dapat menambahkan -o StrictHostKeyChecking=no di ProxyCommand Anda jika Anda menginginkan perilaku itu. Akan sangat tidak bijaksana bagi Ansible untuk mencoba dan memasukkan argumen tambahan ke dalam ProxyCommand di dalam ssh_extra_args yang ditentukan oleh pengguna.

Semua 3 komentar

Ini bukan bug. Anda dapat menambahkan -o StrictHostKeyChecking=no di ProxyCommand Anda jika Anda menginginkan perilaku itu. Akan sangat tidak bijaksana bagi Ansible untuk mencoba dan memasukkan argumen tambahan ke dalam ProxyCommand di dalam ssh_extra_args yang ditentukan oleh pengguna.

Dikonfirmasi, ini berfungsi:

ansible-playbook provision_envs/configure-sid.yml -i inventory/sid --limit=tag_build_5 --vault-password-file ../vault_key --ssh-extra-args='-o StrictHostKeyChecking=no  -o UserKnownHostsFile=/dev/null  -o ProxyCommand="ssh -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -W %h:%p [email protected]"'

mencoba ini dan tidak berhasil ... apakah saya melewatkan sesuatu?

ansible-playbook --private-key aws_key.pem -u ubuntu -e --ssh-extra-args='-o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o ProxyCommand="ssh -o StrictHostKeyChecking=tidak - o UserKnownHostsFile=/dev/null -W %h:%p [email protected] "' -i hosts.txt ./ansible/docker.yml

masih meminta knowhost

Apakah halaman ini membantu?
0 / 5 - 0 peringkat