On 08/19/2016 02:33 PM, Jean-Yves LENHOF wrote:
Le 19/08/2016 à 14:20, Frank Thommen a écrit :
On 08/19/2016 01:54 PM, Jean-Yves LENHOF wrote:
<snip>
The first task ansible is doing is gathering facts.... In facts there
are mounted filesystems, so the NFS one too
[...]
However I found this feature to be quite hidden in the documentation.
IMHO gather_facts should be off by default and only on on request.
Hi,
No it is ok that's on by default and that should stay like this. A lot
of my playbooks (and from other people too) depends on facts
(|ansible_distribution,
||ansible_distribution_version, ||ansible_lsb.major_release, to name the
most currents one....)|
||||
I see it the same as with services, open ports, access permissions ecc.
ecc.: Minimum by default, more on request. But of course, once the
maximum has been established as default, a change can break established
and working mechanisms. Now it's probably too late to change this
initial design decision.
|If you need, you can filter facts :
http://stackoverflow.com/questions/34485286/ansible-gathering-facts-with-filter-inside-a-playbook
But from my point of view, is NFS is not responding, it's your server
that is broken... Perhaps automouting (and so dismounting) NFS is an
option for you Regards, JYL
yes, there is a technical problem, but that's not the issue. The issue
is, that this shouldn't break my scripts. When - very simplified - I
run a script which does an `ls` in my homedirectory I don't want it to
break (rather: it /must/ not break), just because some other, completely
unrelated filesystem or service is not working. But that's what was
happening in our case until we disabled gather_facts.
Anyway: Our current problem is solved - thanks to your hint - and I will
set "gathering = explicit" in the configuration file, which should also
have the desired effect.
Cheers
frank
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/7c2bebb5-f3d7-2fe3-6bda-bbcdd5b7c896%40drosera.ch.
For more options, visit https://groups.google.com/d/optout.