On Thu, 26 Aug 2021 10:08:58 -0400 Brian Coca <bc...@redhat.com> wrote:
> - not running fact gathering It is running. "gather_facts: yes" is set, I even removed cache files to make sure they're re-created. > - fact gathering user not having proper permissions for reading mount > info User is root, so this should always work. > - timeout issues when accessing mount information (common with > shared/network filesystems) Well, there are nfs mounts, but they are all accessible. I even checked them manually now. > - the OS is lying to the standard tools used (commonly happens with > containers) The target is a plain FreeBSD installation on metal. No containers, no virtualization or such. Other FreeBSD hosts report back fine. > - INJECT_FACTS_AS_VARS is set to false, in which case the info will be > in ansible_facts['mounts'] (its always there, inject just adds the > ansible_mounts alias) This isn't set, either. > To find out what exactly is happening i recommend running fact > gathering directly on the targets that you see are missing > ansible_mounts How would I do that? To increase the fun: After some back and forth, removing cache files and re-trying a few times, now it appears to magically work sometimes and sometimes not (especially on one host). This feels like some timing-related issue. The machine in question is under some load, so getting filesystem information might take some time, indeed, due to busy nfs directories. How do I find out on which part fact gathering gets actually stuck, and how do I increase the timeout value for this? cu Gerrit -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/20210826165852.240e0c15%40comet2.terra.ger.
