爲了提供關於安裝的一些上下文,我嘗試使用VirtualBox作爲提供程序和Ansible作爲提供程序從Packer啓動Windows 8.1(x64)VM本地Macbook。我已經使用Packer(沒有Ansible provisioner)測試了Windows版本,該版本可以成功運行。虛擬機中用於Windows 8.1虛擬機的Packer forsible provisioner的問題
但是,當我嘗試使用可靠的配置器(不是本地的)時,我無法這樣做。我已經安裝了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,並得到相同的錯誤。
任何幫助擺脫這個問題將不勝感激。
wth是'parse-args'嗎? – 4c74356b41
它不是一個標準的PowerShell cmdlet,但它似乎可能與Ansible一起提供。它在Git中記錄在這裏:https://github.com/technolo-g/ansible_venv/blob/master/lib/python2.7/site-packages/ansible/module_utils/powershell.ps1 –
「Helper函數來解析Ansible JSON參數從作爲單個參數傳遞給模塊的文件「 –