Windows 的 Ansible:无法通过 WinRM 访问 Windows 机器

Ansible for Windows: Cannot access Windows machine via WinRM

我已经在我的 Linux (14.04) 工作站上安装了 Ansible,还有 Python (2.7.6)、ansible (2.3.0)、pywinrm (0.2.1)。我想使用 Ansible 配置我的 Windows 虚拟机。我在 Azure 中有一个 Windows VM (Win2k12r2)。我已经在 Azure 网络安全组中打开了所有端口,并且在 Windows 防火墙中为 WinRM(5985 和 5986)打开了端口。

我还在我的 Windows VM 中 运行 位于 https://github.com/ansible/ansible/blob/devel/examples/scripts/ConfigureRemotingForAnsible.ps1 的脚本,以确保启用 WinRM。

我能够通过 RDP 进入 Windows 虚拟机,所以我知道它的 public 网络接口正在工作。

根据 ansible 文档 (http://docs.ansible.com/ansible/intro_windows.html) 我有一个清单文件 inventories/test1

[windows]
<azure_ip_address>

我有一个文件 group_vars/windows.yml

ansible_user: <my_user_id>
ansible_password: <azure_vm_password>
ansible_port: 5986
ansible_connection: winrm
# The following is necessary for Python 2.7.9+ when using default WinRM self-signed certificates:
ansible_winrm_server_cert_validation: ignore
ansible_winrm_scheme: https

当我运行命令时:

ansible windows -i inventories/test1 -m win_ping --ask-vault-pass -vvvvv

我收到以下回复:

No config file found; using defaults
Vault password:
Loading callback plugin minimal of type stdout, v2.0 from /home/jgodse/ansible/lib/ansible/plugins/callback/__init__.pyc
Using module file /home/jgodse/ansible/lib/ansible/modules/core/windows/win_ping.ps1
<azure_vm_ip_address> ESTABLISH SSH CONNECTION FOR USER: None
<azure_vm_ip_address> SSH: ansible.cfg set ssh_args: (-C)(-o)(ControlMaster=auto)(-o)(ControlPersist=60s)
<azure_vm_ip_address> SSH: ansible_password/ansible_ssh_pass not set: (-o) (KbdInteractiveAuthentication=no)(-o)(PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey)(-o)(PasswordAuthentication=no)
<azure_vm_ip_address> SSH: ANSIBLE_TIMEOUT/timeout set: (-o)(ConnectTimeout=10)
<azure_vm_ip_address> SSH: PlayContext set ssh_common_args: ()
<azure_vm_ip_address> SSH: PlayContext set ssh_extra_args: ()
<azure_vm_ip_address> SSH: found only ControlPersist; added ControlPath: (-o)(ControlPath=/home/jgodse/.ansible/cp/ansible-ssh-%h-%p-%r)
<azure_vm_ip_address> SSH: EXEC ssh -vvv -C -o ControlMaster=auto -o ControlPersist=60s -o KbdInteractiveAuthentication=no -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey -o PasswordAuthentication=no -o ConnectTimeout=10 -o ControlPath=/home/jgodse/.ansible/cp/ansible-ssh-%h-%p-%r <azure_vm_ip_address> '/bin/sh -c '"'"'( umask 77 && mkdir -p "` echo $HOME/.ansible/tmp/ansible-tmp-1477490434.84-228998637685624 `" && echo ansible-tmp-1477490434.84-228998637685624="` echo $HOME/.ansible/tmp/ansible-tmp-1477490434.84-228998637685624 `" ) && sleep 0'"'"''
<azure_vm_ip_address> | UNREACHABLE! => {
    "changed": false,
    "msg": "Failed to connect to the host via ssh: OpenSSH_6.6.1, OpenSSL 1.0.1f 6 Jan 2014\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 19: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug1: Control socket \"/home/jgodse/.ansible/cp/ansible-ssh-<azure_vm_ip_address>-22-jgodse\" does not exist\r\ndebug2: ssh_connect: needpriv 0\r\ndebug1: Connecting to <azure_vm_ip_address> [<azure_vm_ip_address>] port 22.\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug1: connect to address <azure_vm_ip_address> port 22: Connection timed out\r\nssh: connect to host <azure_vm_ip_address> port 22: Connection timed out\r\n",
    "unreachable": true
}

我尝试远程登录机器如下:

$ telnet <azure_vm_ip_address> 5986
Trying <azure_vm_ip_address>...
Connected to <azure_vm_ip_address>.
Escape character is '^]'.

这告诉我 telnet 工作到 5986,因此我的防火墙规则没有问题。

我是否必须做些什么来告诉 Ansible 我正在尝试使用 WinRM 连接到 Windows 虚拟机?或者我是否遗漏了一些东西来帮助我的 Ansible 工作站通过 WinRM 连接到我的 Windows 虚拟机?

事实证明,将连接变量放在group_vars/windows.yml 中是行不通的。我完全删除了该文件,并将 inventories/test1 编辑为如下所示:

[windows]
<azure_ip_address>

[windows:vars]
ansible_user=<my_user_id>
ansible_password=<azure_vm_password>
ansible_port=5986
ansible_connection=winrm
ansible_winrm_server_cert_validation=ignore

运行 命令有效,运行ning win_ping 成功。

然后我尝试加密 inventories/test1,我得到:

  [WARNING]: No hosts matched, nothing to do

而 win_ping 没有 运行。

此时我的猜测是,连接初始化所需的变量必须在清单文件中,并且在解密和使用加密变量之前读取。