I somewhat remember doing that too, now, but I don't see it in the 
documentation. 

I'm supposed to patch something else in the Windows docs, so I'll add this 
to that patch.

On Thursday, August 28, 2014 3:34:21 PM UTC-5, Damon Overboe wrote:
>
> Found it:
>
> sudo pip install pywinrm
>
> ansible windows -m win_ping
>
> # clone1 | success >> {
>   "changed": false,
>   "ping": "pong"
> }
>
>
>
> On Thursday, August 28, 2014 3:28:31 PM UTC-5, Damon Overboe wrote:
>>
>> OK it is a python problem on my new host, I just don't know / remember 
>> what I did the first time around (if anything) to get winrm.
>>
>> Python still pukes when I tell it to install it, but on my current host, 
>> I ran:
>>
>> find / -name "winrm"
>> # /usr/local/lib/python2.7/dist-packages/winrm
>>
>> Checking on my new host, that directory is missing, so... I'm obviously 
>> missing a dependency.
>>
>> For now, I'm going to try copying that directory over and see how much 
>> havoc I can wreak on that server.
>>
>>
>> On Thursday, August 28, 2014 3:24:57 PM UTC-5, Damon Overboe wrote:
>>>
>>> I have a current Linux control machine that can talk to many Windows 
>>> clients.
>>>
>>> I'm running from source on it (calling `. hacking/env-setup`).
>>>
>>> I'm now trying to bring a new Linux control host (Ubuntu 12.04) online, 
>>> calling the same Windows clients and it's failing.
>>>
>>> Both control hosts have Python 2.7.3.
>>>
>>> I took the same steps setting up this control machine; the pip installs 
>>> of the dependencies went fine.
>>>
>>> But, I'm attempting to win_ping any of the existing clients on the new 
>>> control, and getting the error:
>>>
>>>         FAILED => winrm is not installed
>>>
>>> This control machine is in the same domain as the other control machine, 
>>> and the firewall rules on the Win clients are set to allow Domain (and I 
>>> can ping them successfully).
>>>
>>>
>>>
>>> So, that makes me think, my new Linux control machine must be missing 
>>> winrm;
>>>
>>> But, on both control machines:
>>>
>>> 1. `which winrm` returns nothing
>>> 2. `pip install winrm` fails to find the package
>>> 3. `easy_install winrm` also fails ".."
>>> 4. `apt-get install winrm`: E: Unable to locate package winrm
>>> 5. `find -name "winrm"` returns nothing
>>>
>>>
>>> And `ansible windows -m win_ping -vvvv` doesn't provide any additional 
>>> errors or info.
>>>
>>> So that makes me think it's complaining about the Win clients, but, I 
>>> have them working correctly with the old control already, which is why I 
>>> was looking at the control machine.
>>>
>>>
>>> So next, just in case it is an issue where the clients were caching 
>>> their hosts credentials, I set up a new Win client, and tried connecting to 
>>> it from the new host first.
>>>
>>> I still get the winrm is not installed error.
>>>
>>>
>>> So....... I tested adding a new Win client, and tried connecting to it 
>>> from the new host; no luck, same error. 
>>> I then attempted to connect to it from my old host, and it succeeded; 
>>> ping pong.
>>>
>>> That tells me that there is something wrong with my new control host, 
>>> but I have no idea what else to test or try to install... Any thoughts?
>>>
>>> Here's the code I ran:
>>>
>>> # Copy configs, host files, group_vars from current host to new host;
>>> # /etc/ansible has been created on new host, with appropriate permissions 
>>> for my user
>>> cd /etc/ansible
>>> scp -r * newhost:/etc/ansible
>>> ssh newhost
>>>
>>>
>>> # On new host, prep the tools, pull & launch the source
>>>
>>> sudo pip install paramiko PyYAML jinja2 httplib2
>>>
>>> git clone git://github.com/ansible/ansible.git
>>> cd ./ansible
>>> source ./hacking/env-setup
>>>
>>>
>>> # test it, with the error on the next comment
>>> ansible windows -m win_ping
>>> # clone1 | FAILED => winrm is not installed
>>>
>>>
>>>
>>>

-- 
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/835e69a4-a1c2-4724-8008-2c1a12918328%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to