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:
path: "/home/dev/config"
src: majortom:/diskless/home/devlocal/config
state: "mounted"
opts: "nfsvers=3,tcp,rw"
fstype: "nfs"
---
In this case, /home/dev is already an nfs mount. Strangely, ansible
keeps returning this as "changed", no matter how often I run it.
Changing state to "present" does not show this issue, so the reason
appears to be the mountpoint itself rather than the fstab entry (fstab
is never changed after the first run).
---
TASK [configure nfs mount]
***************************************************** changed: [dev-mx1]
PLAY RECAP
*********************************************************************
dev-mx1 : ok=1 changed=1 unreachable=0
failed=0 skipped=0 rescued=0 ignored=0
---
Any ideas?
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/20211013182336.5d20c9f7%40comet2.terra.ger.
