bigip_device_info errors with - virtual-servers

Question

I am trying to pull an existing description from an existing virtual server using ansible.I found bigip_device_info but am running into errors.&nbsp;I have a ansible yaml file facts.yml:name:&nbsp;Collect&nbsp;BIG-IP&nbsp;information&nbsp;&nbsp;bigip_device_info:&nbsp;&nbsp;&nbsp;&nbsp;provider:&nbsp;"{{&nbsp;provider&nbsp;}}"&nbsp;&nbsp;&nbsp;&nbsp;gather_subset:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;#-&nbsp;virtual-addresses&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;#-&nbsp;ltm-pools&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;-&nbsp;virtual-servers&nbsp;&nbsp;register:&nbsp;bigip_device_info&nbsp;&nbsp;delegate_to:&nbsp;localhost&nbsp;virtual-addresses &amp; ltm-pools both work and return valid information. However virtual-servers always crashes.Will someone please shed some light on this issue and let me know if the syntax is incorrect, is there a bug, etc?&nbsp;Following is the debug error messages with virtual-servers enabled in the yaml file:task path: /home/mboster/cloud-infrastructure/cloudops/infrastructure/network/ansible/waf/roles/mq_deployment/tasks/mq_facts.yml:1&lt;localhost&gt; connection transport is rest&lt;localhost&gt; ESTABLISH LOCAL CONNECTION FOR USER: mboster&lt;localhost&gt; EXEC /bin/sh -c 'echo ~mboster &amp;&amp; sleep 0'&lt;localhost&gt; EXEC /bin/sh -c '( umask 77 &amp;&amp; mkdir -p "` echo /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292 `" &amp;&amp; echo ansible-tmp-1591302659.2270741-189006385395292="` echo /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292 `" ) &amp;&amp; sleep 0'Using module file /usr/local/lib/python3.6/site-packages/ansible/modules/network/f5/bigip_device_info.py&lt;localhost&gt; PUT /home/mboster/.ansible/tmp/ansible-local-73580ev1lcolg/tmphdp8u7ap TO /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292/AnsiballZ_bigip_device_info.py&lt;localhost&gt; EXEC /bin/sh -c 'chmod u+x /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292/ /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292/AnsiballZ_bigip_device_info.py &amp;&amp; sleep 0'&lt;localhost&gt; EXEC /bin/sh -c '/usr/bin/python3 /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292/AnsiballZ_bigip_device_info.py &amp;&amp; sleep 0'&lt;localhost&gt; EXEC /bin/sh -c 'rm -f -r /home/mboster/.ansible/tmp/ansible-tmp-1591302659.2270741-189006385395292/ &gt; /dev/null 2&gt;&amp;1 &amp;&amp; sleep 0'The full traceback is:&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 16259, in main&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 15999, in exec_module&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 16078, in execute_managers&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 15674, in exec_module&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 15682, in _exec_module&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 7092, in to_return&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 15253, in destination_address&nbsp;File "/tmp/ansible_bigip_device_info_payload_b_s1s_gf/ansible_bigip_device_info_payload.zip/ansible/modules/network/f5/bigip_device_info.py", line 15634, in destination_tuple&nbsp;fatal: [ftbc-f5-dev1 -&gt; localhost]: FAILED! =&gt; {&nbsp;&nbsp;&nbsp;"changed": false,&nbsp;&nbsp;&nbsp;"invocation": {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"module_args": {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"gather_subset": [&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"virtual-servers"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;],&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"provider": {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"auth_provider": null,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"server": "ftbc-f5-dev1",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"server_port": 443,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ssh_keyfile": null,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"timeout": null,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"transport": "rest",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"user": "mboster",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"validate_certs": false&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;&nbsp;&nbsp;},&nbsp;&nbsp;&nbsp;"msg": "The provided destination is not a valid IP address"&nbsp;&nbsp;

sachin-garg · Answer

Can you please share your &nbsp; BIG-IP software version &amp; Ansible Version &amp; Python version&nbsp;I can see python3.6&nbsp;bigip_gather_facts has been deprecated /Removed in Ansible version 2.11 (This module has ben removed in version 2.11.&nbsp;[deprecated])&nbsp;The bigip_facts module relies on SOAP to communicate with the BIG-IP, and has a large amount of code that does not conform to existing F5 standards. &nbsp;The&nbsp;bigip_device_info&nbsp;module (Requires BIG-IP software version &gt;= 12) is easier to maintain and use. This module was called&nbsp; bigip_device_facts &nbsp;before Ansible 2.9. The usage did not change.&nbsp;&nbsp;can you provide the output of curling these two APIshttps://IP_ADDRESS/mgmt/tm/sys/software/imagehttps://IP_ADDRESS/mgmt/tm/sys/software/hotfix&nbsp;Please see this section:&nbsp;fatal: [ftbc-f5-dev1 -&gt; localhost]: FAILED! =&gt; {&nbsp;&nbsp;&nbsp;"changed": false,&nbsp;&nbsp;&nbsp;"invocation": {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"module_args": {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"gather_subset": [&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"virtual-servers"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;],&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"provider": {&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"auth_provider": null,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"password": "VALUE_SPECIFIED_IN_NO_LOG_PARAMETER",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"server": "ftbc-f5-dev1",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"server_port": 443,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"ssh_keyfile": null,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"timeout": null,&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"transport": "rest",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"user": "mboster",&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;"validate_certs": false&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;}&nbsp;&nbsp;&nbsp;},&nbsp;&nbsp;&nbsp;"msg": "The provided destination is not a valid IP address"&nbsp;&nbsp;this is the error you're receiving?fatal: [ftbc-f5-dev1 -&gt; localhost]: FAILED! =&gt; {"msg": "The provided destination is not a valid IP address"}&nbsp;It Seems that the partition is not striped correctly since the regex doesn't match numbers and your partition name may contains numbers. Can you please share the names of the partitions.&nbsp;2. validate_certs must be one of: yes,novalidate_certs: False&nbsp;Can you try the latest version:Minimum Ansible Version 2.8&nbsp;https://galaxy.ansible.com/f5devcentral/f5ansible&nbsp;&nbsp;Try these linkshttps://github.com/F5Networks/f5-ansible/issues/1124https://docs.ansible.com/ansible/latest/reference_appendices/common_return_values.html#common-return-valueshttps://clouddocs.f5.com/training/fas-ansible-workshop-101/1.8-virtual-server-facts.htmlhttps://clouddocs.f5.com/products/orchestration/ansible/devel/modules/bigip_device_facts_module.htmlhttps://clouddocs.f5.com/products/orchestration/ansible/devel/modules/bigip_virtual_server_module.html

markbz · Answer

ansible --versionansible 2.9.0&nbsp;config file = /etc/ansible/ansible.cfg&nbsp;configured module search path = ['/home/mboster/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']&nbsp;ansible python module location = /usr/local/lib/python3.6/site-packages/ansible&nbsp;executable location = /usr/local/bin/ansible&nbsp;python version = 3.6.8 (default, Apr&nbsp;2 2020, 13:34:55) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]&nbsp;[mboster@fthc-ctrl-net1 ~]$ python --versionPython 2.7.5&nbsp;target partitiion is /Common&nbsp;list auth partition default-route-domain auth partition AC-PROD {&nbsp;&nbsp;&nbsp;default-route-domain 0}auth partition Common {&nbsp;&nbsp;&nbsp;default-route-domain 0}auth partition test_partition {&nbsp;&nbsp;&nbsp;default-route-domain 0}&nbsp;see attached png file for image. There isn't any hotfix.&nbsp;1. Yes that is the error I am receiving&nbsp;2. validate_certs: no is set in the master_playbook.yml&nbsp;&nbsp;

markbz · Answer

From the master playbook, validate_certs is no, which is where the reported false comes from.&nbsp;&nbsp;vars:&nbsp;&nbsp;&nbsp;&nbsp;provider:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;password:&nbsp;"{{&nbsp;password&nbsp;}}"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;server:&nbsp;"{{&nbsp;inventory_hostname&nbsp;}}"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;user:&nbsp;"{{&nbsp;username&nbsp;}}"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;validate_certs:&nbsp;no&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;server_port:&nbsp;443&nbsp;&nbsp;

darius · Answer

markbz,So are you saying that you can take the exact same playbook and change the information in gather_subset and you get an error ONLY when trying to use "virtual-servers"?This works...
...
    gather_subset:
      - virtual-addresses
...
...but this doesn't?...
...
    gather_subset:
      - virtual-servers
...
...

markbz · Answer

Darius,Yes that is exactly what happens.using - virtual-servers results in a crash.

Forum Discussion

bigip_device_info errors with - virtual-servers

Recent Discussions

user alert on apm logs

Adding New BigIP Units Using Free CPUs on i7800 (LB13 & LB14) to an existing HA Pair

LTM + GTM on same box

How to backup automation Which BIG IP already integration to BIG IQ CM

kerberos authentication on the F5 APM not working

Related Content

Getting error when trying to run Ansible (2.9) playbook using bigip_device_info module

iControl REST Cookbook - Virtual Server (ltm virtual)

Check a Virtual Server's SSL Status

virtual server config

Virtual Server graphical App for F5 LTM