Solution! I owe everyone a big thanks and big apology. It turns out that rpm -e ruby doesn't really rpm -e ruby... Pretty much everything in /usr/lib/ ruby and /usr/lib64/ruby stayed in place when I did that, so when I upgraded ruby and puppet from 0.24.5 to 0.24.8 and ruby from 1.8.1 to 1.8.6, it just overlayed the 1.8.6 files on top of the 1.8.1 instead of removing a bunch of stuff that it should have. In effect, I was really still running puppet 0.24.5 despite the fact that it reported itself as 0.24.8. I removed all the rpms, deleted /usr/lib/ruby and / usr/lib64/ruby and reinstalled and it works as advertised.
And David - you were right. It does fail with the trailing slash :) Thanks again, Mark On Jun 5, 12:56 pm, David Lutterkort <lut...@redhat.com> wrote: > On Fri, 2009-06-05 at 06:02 -0700, Gajillion wrote: > > That didn't work either: > > And I was so convinced it would ;) > > > debug: Augeas[memlock](provider=augeas): sending command 'ins' with > > params ["domain", "after", "/files/etc/security/limits.conf/files/etc/ > > security/limits.conf/domain[last()]"] > > Do you have both a context set and use an absolute path in your changes > now ? The prefix /files/etc/security/limits.conf is duplicated in the > paths - if that still doesn't fix it, can you send the whole limits.conf > file and the augeas resource you use in your manifest ? > > David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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 -~----------~----~----~----~------~----~------~--~---
