On Thu, 26 Aug 2021 12:46:41 -0400
Brian Coca wrote:
> well, 90% of what the timeout does is monitor the mounts (almost
> nothing else has these kind of issues, except networking queries ..
> dns ...)
I see...
> Recent version of ansible are much more verbose and informative about
> the
well, 90% of what the timeout does is monitor the mounts (almost
nothing else has these kind of issues, except networking queries ..
dns ...)
Recent version of ansible are much more verbose and informative about
the mounts, so you should get both warnings and the ansbile_mounts
var, with the
On Thu, 26 Aug 2021 11:28:15 -0400
Brian Coca wrote:
> this seems to be the 'timeout issues' i mentioned above, sometimes
> accessing a mount info, specially NFS mounts, is slow and the
> gathering timeout is hit, try increasing the value (this will also
> probably make fact gathering take
On Thu, 26 Aug 2021 10:08:58 -0400
Brian Coca 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
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
Hello,
I've been using the ansible_mounts variable for quite some time, but
only now I recognise that it is not always defined. Some of my hosts
just return:
---
TASK [debug]
***
ok: [node2] => { "ansible_mounts": "VARIABLE IS NOT
