On Friday, January 10, 2014 5:53:51 AM UTC-6, [email protected] wrote: > > On Friday, January 10, 2014 11:32:59 AM UTC+1, Felix.Frank wrote: > > >> I think your original post to the list was pretty much to the point. > > > I just realized the machine was still running puppet 2.6.18. > I now upgraded to 2.7.23 and I'll wait some runs before filing the issue. > The bug appears to be still there, but the log looks slightly different. > > A v2.6 agent should work with a v2.7 master, but it is worthwhile checking out the effect of the upgrade.
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. John -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/af6b22c6-b348-4ac4-8c29-f2ed53dc145b%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
