On Apr 13, 2:23 am, Patrick <[email protected]> wrote: > It looks to me like yum itself is broken. Try installing something using the > yum command-line client.
Oddly, it looked like we had a problem with one of the repos (404 error), which somehow trickled all the way back. I also put in the 'refreshonly=>true' option into the exec block... restarted puppetmasterd on the server and got a clean catalog run. Now I may have hit another problem. I go onto my pupetmasterserver, and touch / modify the lwm.repo file (removed a bunch of comments). On my client, I kill -USR1 puppetd which forces a catalog rerun, but the file does NOT show up on the client. I have ignorecache=true in both the server and the client puppetd.conf files, and I've restarted the puppetmaster. Both machines are synced via ntp correctly. This seems pretty basic? :) -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
