Thanks Denmat, It was probably crosstalk between gems and RPMs. Turns out that the rubygems RPM was missing some files. Likely cause was accidentally installing and uninstalling rubygems via non-rpm. Reinstalling the RPM fixed the problem. For the benefit of others, here's how we found the problem.
rpm -V <packages> - this checks for pieces missing from the rpm rpm -e --nodeps <package> - this removes the offending package and ignores the dependencies yum install <package> - this reinstalls the package AND rebuilds the dependency tree -- 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 post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
