On 01/10/2014 03:19 PM, jcbollinger wrote: > Myself, I'm stumped. I agree with Felix that it looks like there's a > bug in the provider, but that's not really saying much more than "it > shouldn't do that". I am curious, however, whether Puppet is actually > modifying /etc/fstab on either the failed or the successful run. I am > also curious whether behavior differs when the dodgy Mount is initially > mounted and when it is initially unmounted. None of that really changes > anything, though.
I can add some assumptions :-) The update will likely not change the issue - the mount type and provider have likely not seen much action for a couple of years, code-wise. The root cause for the erratic behavior is likely the fact that the ensure property of the mount type is schizophrenic insofar as to try and sync both the mounting state as well as the content of fstab. The former likely works, but the latter crashes and burns because the leading space breaks the fstab parsing. I cannot yet think of a reason for the agent to oscillate between these behaviors, but it appears "sort of" plausible, or thinkable at least. Cheers, Felix -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/52D00398.9090900%40alumni.tu-berlin.de. For more options, visit https://groups.google.com/groups/opt_out.
