You might be getting bitten by something I fixed in December...

https://github.com/ansible/ansible-modules-core/pull/562

Does it do the same if you use the devel branch?

On Friday, 13 February 2015 15:19:17 UTC, Daniel H wrote:
>
> Can you post the vsphere_guest task that's failing? I can't pick it 
> exactly from that error but we use it a fair bit so can at least have a 
> gander for any of the things we tripped up on while figuring it out.
>
> Cheers,
> Daniel
>
> On Fri, Feb 13, 2015 at 12:56 AM, <[email protected] <javascript:>> wrote:
>
>> I am getting below error while using Ansible (version 1.8.2) 
>> vSphere_guest module,
>>
>> osboxes@osboxes:~$ ansible-playbook /etc/ansible/playbooks/main.yml -K
>> sudo password:
>>
>> PLAY [localhost] 
>> **************************************************************
>>
>> TASK: [vsphere_guest ] 
>> ********************************************************
>> failed: [localhost] => {"failed": true, "parsed": false}
>> SUDO-SUCCESS-ldmjglnajxpocoybboumisekhbbnmhnp
>> Traceback (most recent call last):
>>   File 
>> "/home/osboxes/.ansible/tmp/ansible-tmp-1423728228.54-220175308723408/vsphere_guest",
>>  
>> line 2791, in <module>
>>     main()
>>   File 
>> "/home/osboxes/.ansible/tmp/ansible-tmp-1423728228.54-220175308723408/vsphere_guest",
>>  
>> line 1197, in main
>>     config_check("vm_disk", vm_disk, proto_vm_disk, module)
>>   File 
>> "/home/osboxes/.ansible/tmp/ansible-tmp-1423728228.54-220175308723408/vsphere_guest",
>>  
>> line 1012, in config_check
>>     if diff.recursive_diff():
>>   File 
>> "/home/osboxes/.ansible/tmp/ansible-tmp-1423728228.54-220175308723408/vsphere_guest",
>>  
>> line 983, in recursive_diff
>>     if k in self.check_dict[key]:
>> TypeError: argument of type 'NoneType' is not iterable
>>
>>
>> FATAL: all hosts have already failed -- aborting
>>
>> PLAY RECAP 
>> ********************************************************************
>>            to retry, use: --limit @/home/osboxes/main.retry
>>
>> localhost                  : ok=0    changed=0    unreachable=0   
>>  failed=1
>>
>> Did anybody face this issue before? It may be, I am doing some silly 
>> mistake but unable to catch that.
>>
>> Thanks
>>
>> -- 
>> 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 [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/ansible-project/9778e1a1-fd63-4691-ad7d-41b081e27266%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/ansible-project/9778e1a1-fd63-4691-ad7d-41b081e27266%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/140e75c5-0535-4346-9b79-e2ca90091166%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to