Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Missing facts on Solaris 11.3 (x86) with Ansible 2.4 #31049
setup / gather_facts
OS / ENVIRONMENT
Since Ansible 22.214.171.124 the setup module drops many facts on Solaris 11.3 (x86) systems which were available in Ansible 2.3. CentOS 7.4 seems not to be affected by this issue.
In a quick diff the following facts are missing:
In my case it was
STEPS TO REPRODUCE
ansible all -i inventory.ini -m setup
It seems that older Solaris patchlevels are not affected.
The Solaris evaluation vm from oracle.com has a patchlevel from mid 2015 and can not be upgraded...
While 2017 patchlevel lacks some facts if you use Ansible 126.96.36.199
I'll try to post some setup outputs if I find the time to sanitize them...
- ansible_devices - ansible_memtotal_mb - ansible_mounts - ansible_processor - ansible_processor_cores - ansible_processor_count - ansible_swap_allocated_mb - ansible_swap_reserved_mb - ansible_swapfree_mb - ansible_swaptotal_mb - ansible_uptime_seconds
Those are all from lib/ansible/module_utils/facts/hardware/sunos.py, so if something is causing that module to either fail or get skipped that could cause that. There isnt a good way to narrow it down to which part, so may need to test a view things. If possible, could you include output from some of the commands hardware.py runs to collect sunos facts? That includes: ``` # memory /usr/sbin/prtconf /usr/sbin/swap -s # dmi prtdiag # devices /usr/bin/kstat -p # uptime /usr/bin/kstat -p unix:0:system_misc:snaptime # cpu info /usr/bin/kstat cpu_info # mounts needs the contents of /etc/mtab ```…
On Mon, Oct 16, 2017 at 8:19 AM, passw0rd123 ***@***.***> wrote: It seems that older Solaris patchlevels are not affected. The Solaris evaluation vm from oracle.com has a patchlevel from mid 2015 and can not be upgraded... 0.175.3.1.0.3.0 While 2017 patchlevel lacks some facts if you use Ansible 188.8.131.52 0.175.3.22.0.3.0 I'll try to post some setup outputs if I find the time to sanitize them... — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#31049 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAA7OmlMrLyvRndnK47y-XHyn6LWgHUHks5ss0nFgaJpZM4PnZ-q> .
The correct file is
Is Tab separated and schould work with
If I follow the instructions for the remote debugging of an ansible module, the execution of the setup module on the remote host raises the following error:
I guess this comes from line 240 in
I hope this helps narrowing down the problem.