I can now confirm that Dominic was correct. I'm upgraded to puppet 2.7.16 now and the augeas resources are working. One thing I can also confirm is that Alan's observation about the context not working and to use the full path in the set command was also correct, at least for the sudoers config change I made. However, the other augeas resource I had that was making changes to /etc/ssh/ssh_config worked using the context setting, so I don't know what the problem is there.
In any case, thanks for your help everyone. Cheers, Guy On Saturday, June 16, 2012 12:45:54 AM UTC-7, Dominic Cleal wrote: > > On 15/06/12 22:42, Guy Knights wrote: > > Ok, thanks for your help Alan. BTW, I forgot include our puppet version > > - it's 2.7.0. > > Which version of Augeas are you using? There's a bug if you're using > Augeas 0.10.0 with any version of Puppet before 2.7.10 where it won't > save the resource. You'll need to upgrade Puppet, or downgrade Augeas > to 0.9.0. > > http://projects.puppetlabs.com/issues/11414 > > I think you were saying that Puppet didn't print any errors? This bug > manifests as that, but shows the resource "executing" every time. > > If that's not it, could you please pastebin the logging of the whole > resource when debug was enabled? > > -- > Dominic Cleal > Red Hat Consulting > m: +44 (0)7817 878113 > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/PKSqwJLEZGkJ. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
