short answer: when ansible fact gathering ran and was able to get mount information
long answer: basically what the short answer said, but here are some reasons Ansible was not able to get the information - not running fact gathering - fact gathering user not having proper permissions for reading mount info - timeout issues when accessing mount information (common with shared/network filesystems) - the OS is lying to the standard tools used (commonly happens with containers) - 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) To find out what exactly is happening i recommend running fact gathering directly on the targets that you see are missing ansible_mounts (unless it is the 'inject' issue, which is controller configuration). -- ---------- Brian Coca -- 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/CACVha7fpm9LiRFzXWLyidsEXzCeNT9DePDXJTzhNc9VQqPWh%3DA%40mail.gmail.com.
