Open sathe06 opened 2 years ago
ansible 2.9.15 config file = /etc/ansible/ansible.cfg configured module search path = [u'/users/w661672a/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules'] ansible python module location = /usr/lib/python2.7/site-packages/ansible executable location = /usr/bin/ansible python version = 2.7.18 (default, Sep 30 2020, 13:13:55) [GCC 4.8.5 20150623 (Red Hat 4.8.5-37)]
##### COLLECTION VERSION
This looks like you use vmware_guest_find
that's part of 2.9.15 and not this collection. To tell you the truth, I don't think anyone will work on this. 2.9 (and 2.10, too) will reach EOL next month AFAIK. And since we're a bit short-handed at the moment, I don't think anyone will invest time on fixing this.
Would it be possible for you to test this with a more current Ansible release? Ideally, ansible-core 2.11+ with community 2.2.0 or Ansible 6.0.0 alpha 1 (which I think will be released today or tomorrow).
SUMMARY
We were using vmware_guest_find module to find vm details Scenario: Daily more than 200 vm's this playbook will run. vm_name output value will run with lower/upper sometimes without that. Out of 20 server in a row 4-5 got failed with below error message. If we re-run it again its working as expected. playbook:
we have tried using name as upper-case and without using anything error message:
ISSUE TYPE
COMPONENT NAME
vmware_guest_find
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
Red Hat Enterprise Linux Server release 7.7 (Maipo)
STEPS TO REPRODUCE
EXPECTED RESULTS
{"changed": false, "folders": ["/xxxxxx/vm/Discovered virtual machine"]}
ACTUAL RESULTS