> The RPM for the puppet client came from the Puppet Labs website. I > downloaded the source for 2.7.3, and had to make a few changes to the > SPEC file
(I keep asking this but ...) What OS are you running and version? Where did you get the RPM's for 0.25? Also ... why don't you try these RPM's for 2.7.x: http://yum.puppetlabs.com/el/5/products I think Mike just updated these. > In /var/lib/puppet/client_yaml/catalog/hproxy11.h.sharpcast.com.yaml: > > !ruby/sym content: "--- \n kernelmajversion: \"2.6\"\n processor1: > Intel(R) Xeon(R) CPU L5520 @ 2.27GHz\n hardwareisa: > x86_64\n clientversion: &id001 0.25.5\n processor11: I > > That file is fresh though. It was created after I installed puppet > 2.7.3. Why is puppet saying the client version is 0.25.5? Yeah - thats all synonymous with the behavior we are seeing. The client shows 2.7.3 but the catalogue getting compiled sees 0.25.5. Part of the same mystery I believe ... I'm not sure there is something to gain by seeing this - but maybe. > I've been blowing away /var/lib/puppet when I remove the RPM before > installing the new one. ... but you did not disable pluginsync. There is a difference. It probably won't fix it ... but maybe worth trying. I'm just trying to make sure there is no weird facter plugins. In all honesty I still think this is your environment doing it which is why I'm exploring this kind of thing. Until I can try to replicate the problem myself using the same RPM's and upgrade methodology I have to keep exploring the possibility that something weird is/has happened on your systems that is causing this. ken. -- "Join us for PuppetConf, September 22nd and 23rd in Portland, OR: http://bit.ly/puppetconfsig"; -- 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.
