i have powershell 4 now, but it is still not working porperly. it seems that ansible cannot find my windows.yml file. even if is set those variables in my hosts file, it doesn't work.
Le mardi 23 juin 2015 10:05:14 UTC+1, J Hawkesworth a écrit : > > Maybe try different web browser to download the hotfix? > You either need the hotfix or Windows Management Framework 4.0 as far as I > can tell. > Jon > > On Tuesday, June 23, 2015 at 9:54:31 AM UTC+1, Guillaume Querso wrote: >> >> thank you for your answer, indeed it is not a windows package but sadly >> it didn't solved my problem... >> >> Le mardi 23 juin 2015 00:48:03 UTC+1, Trond Hindenes a écrit : >>> >>> On a side note: To me it looks like you're trying to use the "unarchive" >>> module on a windows node. That won't work. You need to use a module listed >>> in "Windows modules": >>> http://docs.ansible.com/list_of_windows_modules.html >>> >>> On Monday, June 22, 2015 at 5:22:50 PM UTC+2, J Hawkesworth wrote: >>>> >>>> It is a bug in windows management framework which incorrectly sets the >>>> amount of memory available to processes connected via winrm - its really >>>> outside Ansible's domain. >>>> >>>> If you can't install the hotfix another way to get round it is to >>>> install windows managment framework 4, which doesn't have this particular >>>> bug (and has the advantage of giving you powershell 4.0 which has a number >>>> of useful extra features over powershell 3.0). >>>> >>>> Hope this helps >>>> >>>> Jon >>>> >>>> On Monday, June 22, 2015 at 3:17:29 PM UTC+1, Guillaume Querso wrote: >>>>> >>>>> i can't install the hotfix, i am stuck on the terms ans conditions >>>>> page......... >>>>> is this bug related to ansible-playbook because i can make a ping but >>>>> not run my playbook? >>>>> >>>>> Le lundi 22 juin 2015 14:50:22 UTC+1, J Hawkesworth a écrit : >>>>>> >>>>>> Looks like you have hit the windows management framework 3.0 bug >>>>>> described in the blue box here: >>>>>> >>>>>> http://docs.ansible.com/intro_windows.html#windows-system-prep >>>>>> >>>>>> Since win_ping is working for you now, you just need to install the >>>>>> hotfix to get up and running: >>>>>> >>>>>> http://support.microsoft.com/kb/2842230 >>>>>> >>>>>> Jon >>>>>> >>>>>> On Monday, June 22, 2015 at 1:56:30 PM UTC+1, Guillaume Querso wrote: >>>>>>> >>>>>>> i have done this as said in my edit but it is not working for the >>>>>>> playbook. do i have anything else to do to make it run properly? >>>>>>> >>>>>>> Le lundi 22 juin 2015 13:48:43 UTC+1, J Hawkesworth a écrit : >>>>>>>> >>>>>>>> Looks like you just need to add your server into a group called >>>>>>>> windows - the example here shows the group >>>>>>>> http://docs.ansible.com/intro_windows.html#inventory >>>>>>>> >>>>>>>> So your inventory file needs to look like this: >>>>>>>> >>>>>>>> [windows] >>>>>>>> WIN-F6531IBP8HG >>>>>>>> >>>>>>>> The group vars will then take effect for your host and ansible will >>>>>>>> know to connect via winrm instead of ssh, which it is trying at the >>>>>>>> moment >>>>>>>> (which isn't going to work as Windows doesn't understand SSH). >>>>>>>> >>>>>>>> Hope this helps, >>>>>>>> >>>>>>>> Jon >>>>>>>> >>>>>>>> On Monday, June 22, 2015 at 12:46:56 PM UTC+1, Guillaume Querso >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Hello, i am running ansible 1.9.1 on a Ubuntu server 14.04.2, my >>>>>>>>> remote machine is a windows 7 sp1. >>>>>>>>> i have the following files and error message, i don't understand >>>>>>>>> where the issue is.. >>>>>>>>> >>>>>>>>> /etc/ansible/group_vars/windows.yml >>>>>>>>> >>>>>>>>> ansible_ssh_user: AnsibleUser >>>>>>>>> ansible_ssh_pass: ansiblepass >>>>>>>>> ansible_ssh_port: 5986 >>>>>>>>> ansible_connection: winrm >>>>>>>>> >>>>>>>>> /etc/ansible/winplaybook.yml >>>>>>>>> >>>>>>>>> - hosts: WIN-F6531IBP8HG tasks: >>>>>>>>> - name: unarchive unarchive: src=/tmp/hello.txt.zip >>>>>>>>> dest=C:\Users\Querso\Desktop >>>>>>>>> >>>>>>>>> /etc/ansible/hosts >>>>>>>>> >>>>>>>>> WIN-F6531IBP8HG >>>>>>>>> >>>>>>>>> i have python 2.7.6 and i have the following error message: >>>>>>>>> ansible-playbook /etc/ansible/winplaybook.yml -i WIN-F6531IBP8HG, >>>>>>>>> >>>>>>>>> PLAY [WIN-F6531IBP8HG] >>>>>>>>> ******************************************************** >>>>>>>>> >>>>>>>>> GATHERING FACTS >>>>>>>>> *************************************************************** >>>>>>>>> fatal: [WIN-F6531IBP8HG] => SSH Error: Permission denied >>>>>>>>> (publickey,password,keyboard-interactive). >>>>>>>>> while connecting to 192.168.79.133:22 >>>>>>>>> It is sometimes useful to re-run the command using -vvvv, which >>>>>>>>> prints SSH debug output to help diagnose the issue. >>>>>>>>> >>>>>>>>> TASK: [unarchive] >>>>>>>>> ************************************************************* >>>>>>>>> FATAL: no hosts matched or all hosts have already failed -- >>>>>>>>> aborting >>>>>>>>> >>>>>>>>> PLAY RECAP >>>>>>>>> ******************************************************************** >>>>>>>>> to retry, use: --limit @/home/guillaume/winplaybook.retry >>>>>>>>> >>>>>>>>> WIN-F6531IBP8HG : ok=0 changed=0 unreachable=1 failed=0 >>>>>>>>> >>>>>>>>> if i try to ping windows: >>>>>>>>> ansible WIN-F6531IBP8HG -m win_ping >>>>>>>>> WIN-F6531IBP8HG | FAILED => SSH Error: Permission denied >>>>>>>>> (publickey,password,keyboard-interactive). >>>>>>>>> while connecting to 192.168.79.133:22 >>>>>>>>> It is sometimes useful to re-run the command using -vvvv, which >>>>>>>>> prints SSH debug output to help diagnose the issue. >>>>>>>>> >>>>>>>>> thanks for your help!! >>>>>>>>> >>>>>>>> -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/aac93f58-b2f0-429c-9ae7-f9f16ab5e9fc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
