Ansible Playbook using ansible_connection: vmware_tools

Archives Ansible Project
1

Hello.

I am trying to use the ansible_connection: vmware_tools in my playbook. I have been successful in connecting and running basic commands. But I am finding when using modules like yum and there is a long task to do such a patching a linux server after being 1st built the playbook comes back with an error saying “The guest operations agent could not be contacted” and my playbook fails. I go to the server and do a yum update and it’s been fully patched. It seems to me there is a timeout issues waiting for the command to complete.

For the life of me have been unable to find any timeout parameters for the vmtools using the ansible_connection and that fails. When I tried ansible_command_timeout the module also failed.

After the failure I ran the playbook again and it came back saying there was nothing to be done. So I know the command worked and patched the server but still I"m unable to find any kind of timeout parameter for this functionally.

Any ideas?

I know I can use the command with standard SSH connection but I’m trying something new that might help use with other issues. I would like to get the vmtools connection to work as it should and expected to work.

Any help would be appreciated.

Thanks.

Glen

2

This might help…

Here is the pertinent portions of my playbook using the command module…

3

I am using ansible version:

ansible 2.9.15
config file = /etc/ansible/ansible.cfg
configured module search path = [u’/root/.ansible/plugins/modules’, u’/usr/share/ansible/plugins/modules’]
ansible python module location = /usr/lib/python2.7/site-packages/ansible
executable location = /bin/ansible
python version = 2.7.5 (default, Aug 13 2020, 02:51:10) [GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]

Thanks.

Glen

4

Well I feel stupid! This is not a timeout issue but the fact the vmtools is being patched. Something that didn’t cross my mind before looking at all the process during the patching process. Actually saw the command to restart the vmtools agent.

So no issue at all.

Thanks

Glen