WinRM connection error 101

[yop190]

ISSUE TYPE

• Bug Report

COMPONENT NAME

Any win module

ANSIBLE VERSION

ansible 2.3.0.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = Default w/o overrides
  python version = 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609]

CONFIGURATION

Default configuration

OS / ENVIRONMENT

Run in Docker based on williamyeh/ansible:ubuntu16.04

SUMMARY

Since upgrade to 2.3.0, sometimes a communication failure appear with the windows VM

UNREACHABLE! => {"changed": false, "msg": "ssl: HTTPSConnectionPool(host='xxx.xxx.xxx.xxx', port=5986): Max retries exceeded with url: /wsman (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe4220bcd50>: Failed to establish a new connection: [Errno 101] Network is unreachable',))", "unreachable": true}

If I relaunch the playbook, maybe that can run or not;)

STEPS TO REPRODUCE

main.yml
---
- hosts: all
  roles: selenium

roles/selenium/tasks/main.yml
---
  - name: install selenium drivers all
    win_chocolatey: "name=selenium-all-drivers"

  - name: install nssm
    win_chocolatey: "name=nssm"

EXPECTED RESULTS

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: [xxx.xxx.xxx.139]
ok: [xxx.xxx.xxx.141]

TASK [common : install selenium drivers all] ***********************************
ok: [xxx.xxx.xxx.139]
ok: [xxx.xxx.xxx.141]

ACTUAL RESULTS

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
ok: [xxx.xxx.xxx.139]
ok: [xxx.xxx.xxx.141]

TASK [common : install selenium drivers all] ***********************************
fatal: [xxx.xxx.xxx.139]: UNREACHABLE! => {"changed": false, "msg": "ssl: HTTPSConnectionPool(host='xxx.xxx.xxx.139', port=5986): Max retries exceeded with url: /wsman (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe4220bcd50>: Failed to establish a new connection: [Errno 101] Network is unreachable',))", "unreachable": true}
ok: [xxx.xxx.xxx.141]

=========OR======

PLAY [all] *********************************************************************

TASK [Gathering Facts] *********************************************************
fatal: [xxx.xxx.xxx.139]: UNREACHABLE! => {"changed": false, "msg": "ssl: HTTPSConnectionPool(host='xxx.xxx.xxx.139', port=5986): Max retries exceeded with url: /wsman (Caused by NewConnectionError('<requests.packages.urllib3.connection.VerifiedHTTPSConnection object at 0x7fe4220bcd50>: Failed to establish a new connection: [Errno 101] Network is unreachable',))", "unreachable": true}
ok: [xxx.xxx.xxx.141]

TASK [common : install selenium drivers all] ***********************************
ok: [xxx.xxx.xxx.141]

[daBONDi]

Are your Target hosts VirtualBox VM's?
Got the same Problem with some Virtual Box VMs, after long Runtime the Network getting Akward on Windows, the only solutino i found was restarting vm, then it works for like 2-5 hours

[jhawkesworth]

At 19:00 UTC on Tuesday 19 September 2017 this ticket will be processed during the second Windows Sprint,
https://github.com/ansible/community/wiki/Windows:-sprints
we would appreciate if you could join the Sprint to help out with understanding/fixing/closing this issue.

[dagwieers]

So it seems to be a network-related problem rather than a WinRM or Windows related problem (a routing problem or a firewall issue). Maybe even a Docker-related problem (interface issue), or a problem with the Windows host (no longer connected to the network or routing issue to Docker ?).

Can you verify that you can connect to the WinRM port (usually 5986 for HTTPS).

needs_info

[basictheprogram]

Does the information list at provision_docker help?

Specifically adding routes (towards the bottom) ?

[hdansou]

When the driver was installed, the network probably dropped and killed the winrm connection.

[jhawkesworth]

@yop190 Discussed at the sprint call - @hdansou's suggestion above seems plausible as anything that interrupts network connection is likely to break the winrm communications.

Could you try running using async, or via a scheduled task?

needs_info

[dagwieers]

I wonder if this is a recoverable problem, i.e. would a retry with a specific delay overcome this issue ? If so, we could add this, next to "Connection refused" as part of making WinRM a but more resilient. diyan/pywinrm#174 cc: @nitzmahone

[ansibot]

@yop190 This issue is waiting for your response. Please respond or the issue will be closed.

click here for bot help

[jborean93]

Closing as this is a generic user question and a thread already exists to talk about retries after connection refused #25532