On Friday, January 10, 2014 3:19:39 PM UTC+1, jcbollinger wrote: > A v2.6 agent should work with a v2.7 master, but it is worthwhile checking > out the effect of the upgrade. >
The upgrade to 2.7.23 had no effect on the issue. The master runs 3.3.2 by the way; are there issues with this? > 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. > Puppet could never modify /etc/fstab. At the moment I can't check the behaviour with the mount already active. But I discovered a worse effect. The puppet class also includes a yumrepo resource which requires the mount to be active (it adds a local repository pointing at that mount point). Well, the "successful" run does not stop at the failed mount, and it proceeds to actually creating the yum repo config file, thus behaving as if the "require" parameter was ignored! To me it looks like the first failed run leaves the mount resource in a "suspended" state. On the second run puppet just "closes/finishes" it, without actually re-processing the resource from scratch, so it doesn't catch the problems it might have; this time, the processing of the resource is considered to be complete, so puppet proceeds with the other resources and on the next run starts everything from scratch, catching the fstab problem and failing again, and so on. Issue filed: https://tickets.puppetlabs.com/browse/PUP-1415 Marco -- 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/439491a0-1a53-4e12-acc2-cd51df1d569b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
