vmware_guest module Ansible 2.7.4 on latest RHEL 7u6

31 views
Skip to first unread message

Tuyen Nguyen

unread,
Dec 17, 2018, 8:24:53 AM12/17/18
to Ansible Project
Hi

I am getting the following error when I try running a playbook to create a new VM from a template.  It worked before I did yum update on the control server.

The full traceback is:
Traceback (most recent call last):
  File "/root/.ansible/tmp/ansible-tmp-1545052613.45-19770221069605/AnsiballZ_vmware_guest.py", line 113, in <module>
    _ansiballz_main()
  File "/root/.ansible/tmp/ansible-tmp-1545052613.45-19770221069605/AnsiballZ_vmware_guest.py", line 105, in _ansiballz_main
    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)
  File "/root/.ansible/tmp/ansible-tmp-1545052613.45-19770221069605/AnsiballZ_vmware_guest.py", line 48, in invoke_module
    imp.load_module('__main__', mod, module, MOD_DESC)
  File "/tmp/ansible_vmware_guest_payload_9wfO8a/__main__.py", line 2396, in <module>
  File "/tmp/ansible_vmware_guest_payload_9wfO8a/__main__.py", line 2322, in main
  File "/tmp/ansible_vmware_guest_payload_9wfO8a/__main__.py", line 798, in __init__
  File "/tmp/ansible_vmware_guest_payload_9wfO8a/ansible_vmware_guest_payload.zip/ansible/module_utils/vmware.py", line 777, in __init__
AttributeError: 'PyVmomiHelper' object has no attribute 'module'

fatal: [localhost]: FAILED! => {
    "changed": false,
    "module_stderr": "Traceback (most recent call last):\n  File \"/root/.ansible/tmp/ansible-tmp-1545052613.45-19770221069605/AnsiballZ_vmware_guest.py\", line 113, in <module>\n    _ansiballz_main()\n  File \"/root/.ansible/tmp/ansible-tmp-1545052613.45-19770221069605/AnsiballZ_vmware_guest.py\", line 105, in _ansiballz_main\n    invoke_module(zipped_mod, temp_path, ANSIBALLZ_PARAMS)\n  File \"/root/.ansible/tmp/ansible-tmp-1545052613.45-19770221069605/AnsiballZ_vmware_guest.py\", line 48, in invoke_module\n    imp.load_module('__main__', mod, module, MOD_DESC)\n  File \"/tmp/ansible_vmware_guest_payload_9wfO8a/__main__.py\", line 2396, in <module>\n  File \"/tmp/ansible_vmware_guest_payload_9wfO8a/__main__.py\", line 2322, in main\n  File \"/tmp/ansible_vmware_guest_payload_9wfO8a/__main__.py\", line 798, in __init__\n  File \"/tmp/ansible_vmware_guest_payload_9wfO8a/ansible_vmware_guest_payload.zip/ansible/module_utils/vmware.py\", line 777, in __init__\nAttributeError: 'PyVmomiHelper' object has no attribute 'module'\n",
    "module_stdout": "",
    "msg": "MODULE FAILURE\nSee stdout/stderr for the exact error",
    "rc": 1
}

It looks like with the yum update, it updated Ansible to 2.7.4 as well.  On another RHEL7u3 machine with Ansible 2.7.0, the same playbook runs fine.

It seems like something with the updates caused the module to not work correctly. Has anyone seen this issue and how do we resolve it?

Thank in advance.

Dick Visser

unread,
Dec 17, 2018, 11:58:23 AM12/17/18
to ansible...@googlegroups.com
It looks like this issue was introduced after 2.7.2, and fixed in
2.7.5: https://github.com/ansible/ansible/issues/49487.
You're right in between with 2.7.4.
So either downgrade to 2.7.2 or upgrade to 2.7.5.


DIck
> --
> You received this message because you are subscribed to the Google Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/49ac3266-b6ee-4d63-bfca-a57e7dc36a54%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

Tuyen Nguyen

unread,
Dec 17, 2018, 12:57:47 PM12/17/18
to Ansible Project
I see... thanks!  let me find 2.7.5 to upgrade to.

Tuyen Nguyen

unread,
Dec 17, 2018, 1:22:58 PM12/17/18
to Ansible Project
I was previously using Ansible 2.7.0 and I downgraded it back to 2.7.0 and things are working like they were now.  I had another issue where it was not allowing authentication on my account for some reason, and reverting back to 2.7.0 fixed it complete.  


On Monday, December 17, 2018 at 11:58:23 AM UTC-5, Dick Visser wrote:
Reply all
Reply to author
Forward
0 new messages