ANSIBLE Windows 503

586 views
Skip to first unread message

yosser bf

unread,
Feb 24, 2015, 3:08:17 AM2/24/15
to ansible...@googlegroups.com
Hi,

I'm facing an issue trying to launch a simple command "win_ping" to a windows node.
I follow the documentation from the Ansible website.

Windows machine: 
- Windows Server 2012 Standard
- PowerShell 3.0


The errror I got:

# ansible windows -m win_ping -vvvv
<fgr-wgcitmp201> ESTABLISH WINRM CONNECTION FOR USER: devci on PORT 5986 TO fgr-wgcitmp201
<fgr-wgcitmp201> WINRM CONNECT: transport=plaintext endpoint=https://fgr-wgcitmp201:5986/wsman
<fgr-wgcitmp201> WINRM CONNECTION ERROR: 500 WinRMTransport. [Errno 8] _ssl.c:492: EOF occurred in violation of protocol
<fgr-wgcitmp201> WINRM CONNECT: transport=plaintext endpoint=http://fgr-wgcitmp201:5986/wsman
<fgr-wgcitmp201> WINRM CONNECTION ERROR: 500 WinRMTransport. Bad HTTP response returned from server. Code 503, Service Unavailable
fgr-wgcitmp201 | FAILED => 500 WinRMTransport. Bad HTTP response returned from server.  Code 503, Service Unavailable

Any idea ?

yosser bf

unread,
Feb 24, 2015, 11:03:35 AM2/24/15
to ansible...@googlegroups.com

The issue is related to the user in the windows.yml file. The user is on the Domain, it's not yet implemented by Ansible so we have to use a windows user with a domain set on the machine.

If you need domain account. See : http://docs.ansible.com/intro_windows.html#installing-on-the-control-machine

yosser bf

unread,
Feb 24, 2015, 1:15:44 PM2/24/15
to ansible...@googlegroups.com
CORRECTION:
It's implemented by ansible.
If you want to use domain account you have to use kerberos.

See ansible website.
Reply all
Reply to author
Forward
0 new messages