ansible_winrm_read_timeout_sec & ansible_winrm_operation_timeout_sec errors?

Archives Ansible Project
1

$Customer here is confused :slight_smile: using ansible version 2.4.1.0

I get fatal: [redacted-url]: UNREACHABLE! => {"changed": false, "msg": "ssl: a float is required", "unreachable": true}

When I use it in the command line with the following:

ANSIBLE_CONFIG=./ansible.cfg ANSIBLE_FORCE_COLOR=1 PYTHONUNBUFFERED=1 ansible-playbook -v -i ./ansible/hosts -l “TEST_nodes” -e “ansible_user=username ansible_password=password ansible_become_pass=password ansible_port=5986 ansible_connection=winrm ansible_winrm_server_cert_validation=ignore ansible_winrm_read_timeout_sec=150 ansible_winrm_operation_timeout_sec=120” ./ansible/site.yml

Am I not allowed to use it in this way?

(Relevant GitHub issue: https://github.com/ansible/ansible/issues/25539)

2

From that github issue, Dag suggests trying

ansible_winrm_read_timeout_sec=150.0

If that doesn’t work setting all of this stuff
“ansible_user=username ansible_password=password ansible_become_pass=password ansible_port=5986 ansible_connection=winrm ansible_winrm_server_cert_validation=ignore ansible_winrm_read_timeout_sec=150 ansible_winrm_operation_timeout_sec=120”

in your group_vars would save you a lot of typing :-). Since it is going to be true for any windows hosts you have, it one of those things you can probably set once and forget about.

Hope this helps,

Jon

3

Sadly ansible_winrm_read_timeout_sec=150.0 didn’t work

I’ll just add it to the group vars… thanks!

4

New issue raised as dagwieers suggested: https://github.com/ansible/ansible/issues/33339