Giorgio Valoti <[email protected]> writes:
> Michael DeHaan <[email protected]> writes:
>
>> I think the easiest thing to do here would to do a checkout on the machine
>> you are managing and then:
>>
>> source ./hacking/env-setup
>> ./hacking/test-module -m setup
>>
>> And see if that hangs. If that does, it's most likely something in the
>> setup module, rather than a connection issue - which I would say with a
>> large degree of confidence is the case.
>>
>> From there, we can help with some suggestions about how to figure out what
>> part is taking so long to return -- it might not be hanging but just taking
>> a very long time, but we'll see.
>
> You’re right it does not hang.
>
> I retried from my control machine and the gathering facts phase does
> complete after a very long time, a minute or so.
>
> How can I collect additional info in order help you to track down the
> issue?
I’ve tried to gather facts with the setup module from my machine with a
SmartOS zone and I get back the facts, but some are wrong and I am quite
sure that this was *not* the case in the past.
Here are the most obvious errors:
> ansible vm-01.local -i hosts/dev -u root -m setup
vm-01.local | success >> {
"ansible_facts": {
"ansible_distribution": "NA",
"ansible_distribution_major_version": "NA",
"ansible_distribution_release": "NA",
"ansible_distribution_version": "NA",
"ansible_os_family": "NA",
"ansible_pkg_mgr": "macports",
},
"changed": false
}
--
Giorgio Valoti
--
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/m2iohvzial.fsf%40me.com.
For more options, visit https://groups.google.com/d/optout.
