虚拟机中用于Windows 8.1虚拟机的Packer forsible provisioner的问题

Question

为了提供关于安装的一些上下文，我尝试使用VirtualBox作为提供程序和Ansible作为提供程序从Packer启动Windows 8.1（x64）VM本地Macbook。我已经使用Packer（没有Ansible provisioner）测试了Windows版本，该版本可以成功运行。

但是，当我尝试使用可靠的配置器（不是本地的）时，我无法这样做。我已经安装了packer文档中指定的Packer版本：https://www.packer.io/docs/provisioners/ansible.html。 我还在Windows VM的第一次启动时运行http://docs.ansible.com/ansible/intro_windows.html#windows-system-prep上提到的ConfigureRemotingForAnsible.ps1。

我的技术堆栈版本是：

• 帕克1.0.0
• Ansible 2.3.0.0
• 的Python 2.7.11
• pywinrm 0.2.2
• 的VirtualBox 5.1.20

packer.json文件如下

{ 
    "builders": [ 
    { 
     "type": "virtualbox-iso", 
     "iso_url": "{{ user `iso_url` }}", 
     "iso_checksum_type": "sha1", 
     "iso_checksum": "{{ user `iso_checksum` }}", 
     "communicator": "winrm", 
     "headless": "{{ user `headless` }}", 
     "boot_wait": "9m", 
     "winrm_use_ssl": true, 
     "winrm_insecure": true, 
     "winrm_host": "127.0.0.1", 
     "winrm_port": 5986, 
     "winrm_username": "packer", 
     "winrm_password": "packer", 
     "winrm_timeout": "8h", 
     "shutdown_command": "shutdown /s /t 10 /f /d p:4:1 /c \"Packer Shutdown\"", 
     "guest_os_type": "Windows81_64", 
     "guest_additions_mode": "disable", 
     "floppy_files": [ 
     "./answer_files/81/Autounattend.xml", 
     "./scripts/enable-winrm.ps1", 
     "./scripts/ConfigureRemotingForAnsible.ps1" 
     ], 
     "vboxmanage": [ 
     [ "modifyvm", "{{.Name}}", "--natpf1", "winrm,tcp,,5986,,5986" ], 
     [ "modifyvm", "{{.Name}}", "--memory", "4096" ], 
     [ "modifyvm", "{{.Name}}", "--vram", "32" ], 
     [ "modifyvm", "{{.Name}}", "--cpus", "2" ] 
     ] 
    } 
    ], 
    "provisioners": [ 
    { 
     "type": "ansible", 
     "playbook_file": "./provisioner/run-powershell.yml", 
     "local_port": "5986", 
     "user": "packer", 
     "extra_arguments": [ 
     "-vvvv", 
     "--connection", "packer", 
     "--extra-vars", "ansible_shell_type=powershell ansible_shell_executable=None" 
     ] 
    } 
    ], 
    "post-processors": [ 
    { 
     "type": "vagrant", 
     "keep_input_artifact": true, 
     "output": "output-formats/windows_81_{{.Provider}}.box", 
     "vagrantfile_template": "vagrantfile-windows_81.template" 
    } 
    ], 
    "variables": { 
    "headless": "false", 
    "iso_checksum": "CHECKSUM_VALUE", 
    "iso_url": "/path/to/iso" 
    } 
} 

的运行powershell.yml剧本是：

# This playbook tests the script module on Windows hosts 

- name: Run Ansible play 
    hosts: all 
    gather_facts: no 
    tasks: 
    - name: Ping windows machine 
     win_command: cmd.exe /c powershell -Command "Write-Host 'Hello World!'" 
# - name: Ping windows machine 
#  win_ping: 
# - name: Create a file 
#  win_file: 
#  path: "C:\\Windows\\Temp\\ansible_test.txt" 
#  state: touch 
# - name: Run powershell script 
#  script: a:\helloworld.ps1 

所看到的packer.log错误的最终代码段为：

ui: [0;32m virtualbox-iso: <127.0.0.1> (1, '{"exception":"At C:\\\\Users\\\\packer\\\\AppData\\\\Local\\\\Temp\\\\ansible-tmp-1493195766.64-166408222728325\\\\win_command.ps1:25 char:16\\r\\n+ $parsed_args = Parse-Args $args $false\\r\\n+    ~~~~~~~~~~","msg":"The term \\u0027Parse-Args\\u0027 is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.","failed":true}\r\n', 'OpenSSH_6.9p1, LibreSSL 2.1.8\r\ndebug1: Reading configuration data /Users/mk/.ssh/config\r\ndebug1: Reading configuration data /etc/ssh/ssh_config\r\ndebug1: /etc/ssh/ssh_config line 21: Applying options for *\r\ndebug1: auto-mux: Trying existing master\r\ndebug2: fd 3 setting O_NONBLOCK\r\ndebug2: mux_client_hello_exchange: master version 4\r\ndebug3: mux_client_forwards: request forwardings: 0 local, 0 remote\r\ndebug3: mux_client_request_session: entering\r\ndebug3: mux_client_request_alive: entering\r\ndebug3: mux_client_request_alive: done pid = 7498\r\ndebug3: mux_client_request_session: session request sent\r\ndebug1: mux_client_request_session: master session id: 2\r\ndebug3: mux_client_read_packet: read header failed: Broken pipe\r\ndebug2: Received exit status from master 1\r\nShared connection to 127.0.0.1 closed.\r\n')[0m 
ui: [0;32m virtualbox-iso: The full traceback is:[0m 
ui: [0;32m virtualbox-iso: At C:\Users\packer\AppData\Local\Temp\ansible-tmp-1493195766.64-166408222728325\win_command.ps1:25 char:16[0m 
ui: [0;32m virtualbox-iso: + $parsed_args = Parse-Args $args $false[0m 
ui: [0;32m virtualbox-iso: +    ~~~~~~~~~~[0m 
ui: [0;32m virtualbox-iso: fatal: [default]: FAILED! => {[0m 
ui: [0;32m virtualbox-iso:  "changed": false,[0m 
ui: [0;32m virtualbox-iso:  "failed": true,[0m 
ui: [0;32m virtualbox-iso:  "msg": "The term 'Parse-Args' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again."[0m 
ui: [0;32m virtualbox-iso: }[0m 
ui: [0;32m virtualbox-iso: to retry, use: --limit @/Users/mk/Workspace/packer/win81/provisioner/run-powershell.retry[0m 
ui: [0;32m virtualbox-iso:[0m 
ui: [0;32m virtualbox-iso: PLAY RECAP *********************************************************************[0m 
ui: [0;32m virtualbox-iso: default     : ok=0 changed=0 unreachable=0 failed=1[0m 
ui: [0;32m virtualbox-iso:[0m 
packer: 2017/04/26 18:36:31 shutting down the SSH proxy 
packer: 2017/04/26 18:36:31 Executing VBoxManage: []string{"controlvm", "packer-virtualbox-iso-1493195197", "poweroff"} 

的ansible窗口任务无（在Windows虚拟机上以.ps1执行）能够执行，并且会收到与上述相同的错误（请参阅我的操作手册中的注释行）。它们都是Parse-Args cmdlet上的错误，这是一个标准的Powershell函数，但由于某些原因无法在Windows 8.1 vm上识别。

仅供参考：我也尝试在端口5985（没有SSL）上运行winrm，并得到相同的错误。

任何帮助摆脱这个问题将不胜感激。

Answer 1

是否有同样的确切问题。我发现最近版本的Ansible中爆出了一些东西。我将Ansible安装降级到2.2.0，并按照Packer文档的预期工作。