Hello,
It looks like the mount module always returns "changed" for me on a
nfs mountpoint that is stacked onto another mountpoint. Is this an
intended behaviour, or am I doing something wrong?
I have created the following "minimal" test task:
---
- name: configure nfs mount
mount:
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
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
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
On Fri, 18 Sep 2020 09:41:56 +0200
"'Felix Fontein' via Ansible Development"
wrote:
> > ---
> > copy_links: Copy symlinks as the item that they point to (the
> > referent) is copied, rather than the symlink.
> >
> > links: Copy symlinks as symlinks.
> > ---
> >
> > This looks rather
Hello,
I have a question concerning the handling of symlinks with the
synchronize module:
What exactly is the difference between the "link" and "copy_link"
options, and how are they intended to be used? The docs say
---
copy_links: Copy symlinks as the item that they point to (the referent)
is
