Maybe it''s because it''s Friday, but I''m suddenly not
sure if I am
going crazy or not...
I have a server running 2.7.3, and clients running 0.25.5. As part of
my attempt to upgrade the clients, I''m using mcollective to upgrade
the puppet package. After doing that, I''m using the $puppetversion
facter variable to determine what version of puppet the client has,
and push out the version appropriate puppet.conf file.
Putting this into the manifest:
notice ("fqdn = $fqdn, puppetversion = $puppetversion")
I''m seeing this in the server logs:
fqdn = hproxy10.h.foo.com, puppetversion = 0.25.5
Now, that''s awfully strange, since on the client:
[root@hproxy10 ~]# facter | grep puppetversion
puppetversion => 2.7.3
What''s up with that?
Doug
(hoping this post doesn''t offend Mr Pienaar)
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
''notice'' is a function. It runs on the server. Try using the ''notify'' resource instead. ken. On Sat, Sep 10, 2011 at 12:24 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> Maybe it''s because it''s Friday, but I''m suddenly not sure if I am > going crazy or not... > > I have a server running 2.7.3, and clients running 0.25.5. As part of > my attempt to upgrade the clients, I''m using mcollective to upgrade > the puppet package. After doing that, I''m using the $puppetversion > facter variable to determine what version of puppet the client has, > and push out the version appropriate puppet.conf file. > > Putting this into the manifest: > notice ("fqdn = $fqdn, puppetversion = $puppetversion") > > I''m seeing this in the server logs: > fqdn = hproxy10.h.foo.com, puppetversion = 0.25.5 > > Now, that''s awfully strange, since on the client: > > [root@hproxy10 ~]# facter | grep puppetversion > puppetversion => 2.7.3 > > What''s up with that? > > Doug > (hoping this post doesn''t offend Mr Pienaar) > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- "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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:27 PM, Ken Barber <ken@puppetlabs.com> wrote:> ''notice'' is a function. It runs on the server. Try using the ''notify'' > resource instead.I think you misunderstood my question. I''m using notice() just for debugging purposes, and it''s always behaved in the past as if running on the client. The FQDN is also evaluating to the correct value for the client. Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> ''notice'' is a function. It runs on the server. Try using the ''notify'' > resource instead.but surely those two variables would be based on the facts and not some master state? notify would run on the node yes, but the resolution of variable to string would still happen on the master. somethings very fishy.> > (hoping this post doesn''t offend Mr Pienaar)the detailed problem description without the drama is a huge improvement, thank you -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> ''notice'' is a function. It runs on the server. Try using the ''notify'' >> resource instead. > > but surely those two variables would be based on the facts and not some > master state? > > notify would run on the node yes, but the resolution of variable to string > would still happen on the master. > > somethings very fishy.Yeah - I just realised my mistake after I sent the message :-). Sorry. Can I just clarify this:> clients running 0.25.5Which one is which? Because your facter output on the client you tested showed 2.7.3 right? It does sound very fishy indeed.>> > (hoping this post doesn''t offend Mr Pienaar) > > the detailed problem description without the drama is a huge improvement, > thank youSpeaking for myself I agree. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:36 PM, Ken Barber <ken@puppetlabs.com> wrote:>>> ''notice'' is a function. It runs on the server. Try using the ''notify'' >>> resource instead. >> >> but surely those two variables would be based on the facts and not some >> master state? >> >> notify would run on the node yes, but the resolution of variable to string >> would still happen on the master. >> >> somethings very fishy. > > Yeah - I just realised my mistake after I sent the message :-). Sorry. > > Can I just clarify this: > >> clients running 0.25.5 > > Which one is which? Because your facter output on the client you > tested showed 2.7.3 right? > > It does sound very fishy indeed.Yes, running this on the client: [root@hproxy10 ~]# facter | grep puppetversion puppetversion => 2.7.3 [root@hproxy10 ~]# rpm -qa | grep puppet puppet-2.7.3-1 [root@hproxy10 ~]# rpm -qa | grep facter facter-1.6.0-1 Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
What does:
puppet -e ''notice("$puppetversion")''
Show on the _client_? I know its probably obvious but you never know.
ken.
On Sat, Sep 10, 2011 at 12:39 AM, Douglas Garstang
<doug.garstang@gmail.com> wrote:> On Fri, Sep 9, 2011 at 4:36 PM, Ken Barber <ken@puppetlabs.com>
wrote:
>>>> ''notice'' is a function. It runs on the
server. Try using the ''notify''
>>>> resource instead.
>>>
>>> but surely those two variables would be based on the facts and not
some
>>> master state?
>>>
>>> notify would run on the node yes, but the resolution of variable to
string
>>> would still happen on the master.
>>>
>>> somethings very fishy.
>>
>> Yeah - I just realised my mistake after I sent the message :-). Sorry.
>>
>> Can I just clarify this:
>>
>>> clients running 0.25.5
>>
>> Which one is which? Because your facter output on the client you
>> tested showed 2.7.3 right?
>>
>> It does sound very fishy indeed.
>
> Yes, running this on the client:
>
> [root@hproxy10 ~]# facter | grep puppetversion
> puppetversion => 2.7.3
>
> [root@hproxy10 ~]# rpm -qa | grep puppet
> puppet-2.7.3-1
>
> [root@hproxy10 ~]# rpm -qa | grep facter
> facter-1.6.0-1
>
> Doug.
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>
--
"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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> wrote:> What does: > > puppet -e ''notice("$puppetversion")'' > > Show on the _client_? I know its probably obvious but you never know. >Actually, it''s not obvious. I didn''t know you could do that. Never seen it documented anywhere... But, [root@hproxy10 ~]# puppet -e ''notice("$puppetversion")'' warning: Implicit invocation of ''puppet apply'' by passing files (or flags) directly to ''puppet'' is deprecated, and will be removed in the 2.8 series. Please invoke ''puppet apply'' directly in the future. warning: You have configuration parameter $localconfig specified in [puppetd], which is a deprecated section. I''m assuming you meant [agent] warning: You have configuration parameter $classfile specified in [puppetd], which is a deprecated section. I''m assuming you meant [agent] warning: You have configuration parameter $report specified in [puppetd], which is a deprecated section. I''m assuming you meant [agent] notice: Scope(Class[main]): 2.7.3 notice: Finished catalog run in 0.21 seconds Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On the same box, what does puppet agent --version give you? -Eric On Friday, September 9, 2011 at 7:47 PM, Douglas Garstang wrote:> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com (mailto:ken@puppetlabs.com)> wrote: > > What does: > > > > puppet -e ''notice("$puppetversion")'' > > > > Show on the _client_? I know its probably obvious but you never know. > > Actually, it''s not obvious. I didn''t know you could do that. Never > seen it documented anywhere... > > But, > > > [root@hproxy10 ~]# puppet -e ''notice("$puppetversion")'' > warning: Implicit invocation of ''puppet apply'' by passing files (or > flags) directly > to ''puppet'' is deprecated, and will be removed in the 2.8 series. Please > invoke ''puppet apply'' directly in the future. > > warning: You have configuration parameter $localconfig specified in > [puppetd], which is a deprecated section. I''m assuming you meant > [agent] > warning: You have configuration parameter $classfile specified in > [puppetd], which is a deprecated section. I''m assuming you meant > [agent] > warning: You have configuration parameter $report specified in > [puppetd], which is a deprecated section. I''m assuming you meant > [agent] > notice: Scope(Class[main]): 2.7.3 > notice: Finished catalog run in 0.21 seconds > > Doug > > -- > 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 (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto:puppet-users+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> > wrote: > > What does: > > > > puppet -e ''notice("$puppetversion")'' > > > > Show on the _client_? I know its probably obvious but you never > > know. > > > > Actually, it''s not obvious. I didn''t know you could do that. Never > seen it documented anywhere...> notice: Scope(Class[main]): 2.7.3 > notice: Finished catalog run in 0.21 secondsif you change the notice() in your manifests to notify{"${puppetversion} on ${fqdn}":} and run puppet agent --test on the node, does it still give the wrong version? -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:48 PM, Eric Shamow <eric@puppetlabs.com> wrote:> On the same box, what does > > puppet agent --version > > give you? >That gives me: [root@hproxy10 ~]# puppet agent --version 2.7.3 Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> puppet -e ''notice("$puppetversion")'' >> >> Show on the _client_? I know its probably obvious but you never know. >> > > Actually, it''s not obvious. I didn''t know you could do that. Never > seen it documented anywhere...puppet help apply (I really should use puppet apply these days as that way of using -e is deprecated).> [root@hproxy10 ~]# puppet -e ''notice("$puppetversion")'' > notice: Scope(Class[main]): 2.7.3 > notice: Finished catalog run in 0.21 secondsYeah - that doesn''t help. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Right, so your client is running 2.7.3, not 0.25. That''s why faster is returning 2.7.3. On the master try running the same. If it doesn''t work try puppetd --version -Eric On Friday, September 9, 2011 at 7:50 PM, Douglas Garstang wrote:> On Fri, Sep 9, 2011 at 4:48 PM, Eric Shamow <eric@puppetlabs.com (mailto:eric@puppetlabs.com)> wrote: > > On the same box, what does > > > > puppet agent --version > > > > give you? > > That gives me: > > [root@hproxy10 ~]# puppet agent --version > 2.7.3 > > Doug > > -- > 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 (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto:puppet-users+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:50 PM, R.I.Pienaar <rip@devco.net> wrote:> > > ----- Original Message ----- >> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> >> wrote: >> > What does: >> > >> > puppet -e ''notice("$puppetversion")'' >> > >> > Show on the _client_? I know its probably obvious but you never >> > know. >> > >> >> Actually, it''s not obvious. I didn''t know you could do that. Never >> seen it documented anywhere... > >> notice: Scope(Class[main]): 2.7.3 >> notice: Finished catalog run in 0.21 seconds > > if you change the notice() in your manifests to notify{"${puppetversion} on ${fqdn}":} > and run puppet agent --test on the node, does it still give the wrong version?Changing the notice line to: notice ("fqdn = ${fqdn}, puppetversion = ${puppetversion}") still gives (on the master): Sep 9 16:52:09 sv2admin1 puppet-master[14087]: (Scope(Class[Puppet::Setup])) fqdn = hproxy10.h.foo.com, puppetversion = 0.25.5 I assume you mean''t to use notify(), not notify{} .... ? Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:52 PM, Eric Shamow <eric@puppetlabs.com> wrote:> Right, so your client is running 2.7.3, not 0.25. That''s why faster is returning 2.7.3. > > On the master try running the same. If it doesn''t work tryYou got that a bit mixed up... The server and client are both running 2.7.3, but the $puppetversion facter variable is returning 0.25.5 on the master. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> On Fri, Sep 9, 2011 at 4:50 PM, R.I.Pienaar <rip@devco.net> wrote: > > > > > > ----- Original Message ----- > >> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> > >> wrote: > >> > What does: > >> > > >> > puppet -e ''notice("$puppetversion")'' > >> > > >> > Show on the _client_? I know its probably obvious but you never > >> > know. > >> > > >> > >> Actually, it''s not obvious. I didn''t know you could do that. Never > >> seen it documented anywhere... > > > >> notice: Scope(Class[main]): 2.7.3 > >> notice: Finished catalog run in 0.21 seconds > > > > if you change the notice() in your manifests to > > notify{"${puppetversion} on ${fqdn}":} > > and run puppet agent --test on the node, does it still give the > > wrong version? > > Changing the notice line to: > notice ("fqdn = ${fqdn}, puppetversion = ${puppetversion}") > > still gives (on the master): > Sep 9 16:52:09 sv2admin1 puppet-master[14087]: > (Scope(Class[Puppet::Setup])) fqdn = hproxy10.h.foo.com, > puppetversion > = 0.25.5 > > I assume you mean''t to use notify(), not notify{} .... ?no, i did mean use notify :) -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> I assume you mean''t to use notify(), not notify{} .... ?No - he meant what he said. Its a resource for client notifications. Give it a try can''t hurt. Can you send your puppet.conf from both boxes (via pastie or somesuch)? Maybe there is something there. I''m tempted to suggest running the puppet master in the foreground to see if it might shake something up but maybe its a little hard-core for now. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Out of morbid curiosity - how are you running the puppet client on that client box? You aren''t running an agent are you and using kick or some such? On Sat, Sep 10, 2011 at 12:56 AM, Ken Barber <ken@puppetlabs.com> wrote:>> I assume you mean''t to use notify(), not notify{} .... ? > > No - he meant what he said. Its a resource for client notifications. > Give it a try can''t hurt. > > Can you send your puppet.conf from both boxes (via pastie or > somesuch)? Maybe there is something there. I''m tempted to suggest > running the puppet master in the foreground to see if it might shake > something up but maybe its a little hard-core for now. > > ken. > > -- > "Join us for PuppetConf, September 22nd and 23rd in Portland, OR: > http://bit.ly/puppetconfsig" >-- "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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
I remember seeing a bug that''s somewhat similar to this, but I don''t know if it''s related --> https://projects.puppetlabs.com/issues/9289 On Fri, Sep 9, 2011 at 5:00 PM, Ken Barber <ken@puppetlabs.com> wrote:> Out of morbid curiosity - how are you running the puppet client on > that client box? You aren''t running an agent are you and using kick or > some such? > > On Sat, Sep 10, 2011 at 12:56 AM, Ken Barber <ken@puppetlabs.com> wrote: > >> I assume you mean''t to use notify(), not notify{} .... ? > > > > No - he meant what he said. Its a resource for client notifications. > > Give it a try can''t hurt. > > > > Can you send your puppet.conf from both boxes (via pastie or > > somesuch)? Maybe there is something there. I''m tempted to suggest > > running the puppet master in the foreground to see if it might shake > > something up but maybe its a little hard-core for now. > > > > ken. > > > > -- > > "Join us for PuppetConf, September 22nd and 23rd in Portland, OR: > > http://bit.ly/puppetconfsig" > > > > > > -- > "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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- Gary Larizza Professional Services Engineer Puppet Labs Join us for PuppetConf <http://bit.ly/puppetconfsig>, September 22nd and 23rd in Portland, OR! -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Crap...nevermind - that''s a dashboard issue. On Fri, Sep 9, 2011 at 5:00 PM, Ken Barber <ken@puppetlabs.com> wrote:> Out of morbid curiosity - how are you running the puppet client on > that client box? You aren''t running an agent are you and using kick or > some such? > > On Sat, Sep 10, 2011 at 12:56 AM, Ken Barber <ken@puppetlabs.com> wrote: > >> I assume you mean''t to use notify(), not notify{} .... ? > > > > No - he meant what he said. Its a resource for client notifications. > > Give it a try can''t hurt. > > > > Can you send your puppet.conf from both boxes (via pastie or > > somesuch)? Maybe there is something there. I''m tempted to suggest > > running the puppet master in the foreground to see if it might shake > > something up but maybe its a little hard-core for now. > > > > ken. > > > > -- > > "Join us for PuppetConf, September 22nd and 23rd in Portland, OR: > > http://bit.ly/puppetconfsig" > > > > > > -- > "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+unsubscribe@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/puppet-users?hl=en. > >-- Gary Larizza Professional Services Engineer Puppet Labs Join us for PuppetConf <http://bit.ly/puppetconfsig>, September 22nd and 23rd in Portland, OR! -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 4:55 PM, R.I.Pienaar <rip@devco.net> wrote:> > > ----- Original Message ----- >> On Fri, Sep 9, 2011 at 4:50 PM, R.I.Pienaar <rip@devco.net> wrote: >> > >> > >> > ----- Original Message ----- >> >> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> >> >> wrote: >> >> > What does: >> >> > >> >> > puppet -e ''notice("$puppetversion")'' >> >> > >> >> > Show on the _client_? I know its probably obvious but you never >> >> > know. >> >> > >> >> >> >> Actually, it''s not obvious. I didn''t know you could do that. Never >> >> seen it documented anywhere... >> > >> >> notice: Scope(Class[main]): 2.7.3 >> >> notice: Finished catalog run in 0.21 seconds >> > >> > if you change the notice() in your manifests to >> > notify{"${puppetversion} on ${fqdn}":} >> > and run puppet agent --test on the node, does it still give the >> > wrong version? >> >> Changing the notice line to: >> notice ("fqdn = ${fqdn}, puppetversion = ${puppetversion}") >> >> still gives (on the master): >> Sep 9 16:52:09 sv2admin1 puppet-master[14087]: >> (Scope(Class[Puppet::Setup])) fqdn = hproxy10.h.foo.com, >> puppetversion >> = 0.25.5 >> >> I assume you mean''t to use notify(), not notify{} .... ? > > no, i did mean use notify :)Ok, using notify{}, the client now says: Sep 9 17:13:38 hproxy10 puppet-agent[30537]: 0.25.5 on hproxy10.h.foo.com Sep 9 17:13:38 hproxy10 puppet-agent[30537]: (/Stage[main]/Puppet::Setup/Notify[0.25.5 on hproxy10.h.foo.com]/message) defined ''message'' as ''0.25.5 on hproxy10.h.foo.com'' I know I''ll get slammed for asking, but where is the use of notify{} in this manner documented? I didn''t know you could do that. WHat does notify do? As far as the docs are concerned, it''s a resource type. Interestingly, it returns 0.25.5... Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Notify is a resource, notice() is a function. So notice() is evaluated on the
server, whereas notify{} is evaluated on the client.
My suspicion is that you somehow have two versions of the client binary hanging
around. Perhaps one that is running when you execute "puppet" at the
shell, and another running in the background.
Per Ken''s question - how are you launching Puppet? Is it as a service?
Or are you running it from a cron job?
-Eric
On Friday, September 9, 2011 at 8:16 PM, Douglas Garstang wrote:
> On Fri, Sep 9, 2011 at 4:55 PM, R.I.Pienaar <rip@devco.net
(mailto:rip@devco.net)> wrote:
> >
> >
> > ----- Original Message -----
> > > On Fri, Sep 9, 2011 at 4:50 PM, R.I.Pienaar <rip@devco.net
(mailto:rip@devco.net)> wrote:
> > > >
> > > >
> > > > ----- Original Message -----
> > > > > On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber
<ken@puppetlabs.com (mailto:ken@puppetlabs.com)>
> > > > > wrote:
> > > > > > What does:
> > > > > >
> > > > > > puppet -e
''notice("$puppetversion")''
> > > > > >
> > > > > > Show on the _client_? I know its probably obvious
but you never
> > > > > > know.
> > > > >
> > > > > Actually, it''s not obvious. I didn''t
know you could do that. Never
> > > > > seen it documented anywhere...
> > > >
> > > > > notice: Scope(Class[main]): 2.7.3
> > > > > notice: Finished catalog run in 0.21 seconds
> > > >
> > > > if you change the notice() in your manifests to
> > > > notify{"${puppetversion} on ${fqdn}":}
> > > > and run puppet agent --test on the node, does it still give
the
> > > > wrong version?
> > >
> > > Changing the notice line to:
> > > notice ("fqdn = ${fqdn}, puppetversion =
${puppetversion}")
> > >
> > > still gives (on the master):
> > > Sep 9 16:52:09 sv2admin1 puppet-master[14087]:
> > > (Scope(Class[Puppet::Setup])) fqdn = hproxy10.h.foo.com
(http://hproxy10.h.foo.com),
> > > puppetversion
> > > = 0.25.5
> > >
> > > I assume you mean''t to use notify(), not notify{} .... ?
> >
> > no, i did mean use notify :)
>
> Ok, using notify{}, the client now says:
>
> Sep 9 17:13:38 hproxy10 puppet-agent[30537]: 0.25.5 on hproxy10.h.foo.com
(http://hproxy10.h.foo.com)
> Sep 9 17:13:38 hproxy10 puppet-agent[30537]:
> (/Stage[main]/Puppet::Setup/Notify[0.25.5 on
> hproxy10.h.foo.com (http://hproxy10.h.foo.com)]/message) defined
''message'' as ''0.25.5 on
> hproxy10.h.foo.com (http://hproxy10.h.foo.com)''
>
> I know I''ll get slammed for asking, but where is the use of
notify{}
> in this manner documented? I didn''t know you could do that. WHat
does
> notify do? As far as the docs are concerned, it''s a resource type.
>
> Interestingly, it returns 0.25.5...
>
> Doug.
>
> --
> 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
(mailto:puppet-users@googlegroups.com).
> To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com
(mailto:puppet-users+unsubscribe@googlegroups.com).
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> On Fri, Sep 9, 2011 at 4:55 PM, R.I.Pienaar <rip@devco.net> wrote: > > > > > > ----- Original Message ----- > >> On Fri, Sep 9, 2011 at 4:50 PM, R.I.Pienaar <rip@devco.net> wrote: > >> > > >> > > >> > ----- Original Message ----- > >> >> On Fri, Sep 9, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> > >> >> wrote: > >> >> > What does: > >> >> > > >> >> > puppet -e ''notice("$puppetversion")'' > >> >> > > >> >> > Show on the _client_? I know its probably obvious but you > >> >> > never > >> >> > know. > >> >> > > >> >> > >> >> Actually, it''s not obvious. I didn''t know you could do that. > >> >> Never > >> >> seen it documented anywhere... > >> > > >> >> notice: Scope(Class[main]): 2.7.3 > >> >> notice: Finished catalog run in 0.21 seconds > >> > > >> > if you change the notice() in your manifests to > >> > notify{"${puppetversion} on ${fqdn}":} > >> > and run puppet agent --test on the node, does it still give the > >> > wrong version? > >> > >> Changing the notice line to: > >> notice ("fqdn = ${fqdn}, puppetversion = ${puppetversion}") > >> > >> still gives (on the master): > >> Sep 9 16:52:09 sv2admin1 puppet-master[14087]: > >> (Scope(Class[Puppet::Setup])) fqdn = hproxy10.h.foo.com, > >> puppetversion > >> = 0.25.5 > >> > >> I assume you mean''t to use notify(), not notify{} .... ? > > > > no, i did mean use notify :) > > Ok, using notify{}, the client now says: > > Sep 9 17:13:38 hproxy10 puppet-agent[30537]: 0.25.5 on > hproxy10.h.foo.com > Sep 9 17:13:38 hproxy10 puppet-agent[30537]: > (/Stage[main]/Puppet::Setup/Notify[0.25.5 on > hproxy10.h.foo.com]/message) defined ''message'' as ''0.25.5 on > hproxy10.h.foo.com''stumped, this is totally f''d up :) how do you create the node? with an ENC or with node foo {} blocks?> I know I''ll get slammed for asking, but where is the use of notify{} > in this manner documented? I didn''t know you could do that. WHat does > notify do? As far as the docs are concerned, it''s a resource type.yeah so notice() is a function, functions run on the puppet master and so you find them in the syslog or whatever. They get evaluated at compile time But this doesnt help if you wanted to log on the node, or give someone running puppetd --test some interactive feedback *on the node* types and providers are the only thing that really ''runs'' on a node, so notify being a resource means you can emit text to the client side and it shows what would be the result of the compiled catalog. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 5:18 PM, Eric Shamow <eric@puppetlabs.com> wrote:> Notify is a resource, notice() is a function. So notice() is evaluated on the server, whereas notify{} is evaluated on the client. > > My suspicion is that you somehow have two versions of the client binary hanging around. Perhaps one that is running when you execute "puppet" at the shell, and another running in the background. > > Per Ken''s question - how are you launching Puppet? Is it as a service? Or are you running it from a cron job?I know that notice() is a function, and notify{} is a resource. The documentation says that much. However, it doesn''t really go beyond that. The documentation provides examples of how to use notify{} to notify another resource when it changes, but I don''t believe it gives you any indication whatsoever that you can use it in a stand alone fashion like this. Where is that use documented? How would anyone except the core puppet developers know that you could even do this? I''m launching puppet with ''service puppet restart''. What libraries? If you know their names I can search for them. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> I know that notice() is a function, and notify{} is a resource. The > documentation says that much. However, it doesn''t really go beyond > that. The documentation > provides examples of how to use notify{} to notify another resource > when it changes, but I don''t believe it gives you any indication > whatsoever that you can use it in a stand alone fashion like this. > Where is that use documented? How would anyone except the core puppet > developers know that you could even do this?You are confusing the notify attribute with the notify{} type. http://docs.puppetlabs.com/references/stable/type.html#notify This is different from file { "foo": notify => bar, }> I''m launching puppet with ''service puppet restart''. What libraries? If > you know their names I can search for them.So you are running it as a service, then. Please paste the results of the following two commands: which puppet pgrep puppet -Eric -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> On Fri, Sep 9, 2011 at 5:18 PM, Eric Shamow <eric@puppetlabs.com> > wrote: > > Notify is a resource, notice() is a function. So notice() is > > evaluated on the server, whereas notify{} is evaluated on the > > client. > > > > My suspicion is that you somehow have two versions of the client > > binary hanging around. Perhaps one that is running when you > > execute "puppet" at the shell, and another running in the > > background. > > > > Per Ken''s question - how are you launching Puppet? Is it as a > > service? Or are you running it from a cron job? > > I know that notice() is a function, and notify{} is a resource. The > documentation says that much. However, it doesn''t really go beyond > that. The documentation > provides examples of how to use notify{} to notify another resource > when it changes, but I don''t believe it gives you any indication > whatsoever that you can use it in a stand alone fashion like this. > Where is that use documented? How would anyone except the core puppet > developers know that you could even do this?I think you are confusing server{"foo": notify => Service["bar"]} with the resource called notify that you can see documented here: http://docs.puppetlabs.com/references/stable/type.html#notify> > I''m launching puppet with ''service puppet restart''. What libraries? > If you know their names I can search for them.on the node in question, did you perhaps have a puppet installed by rubygem and then later with rpm/deb, or always only used the one method and upgraded that using the same -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Fri, Sep 9, 2011 at 5:50 PM, R.I.Pienaar <rip@devco.net> wrote:> > > ----- Original Message ----- >> On Fri, Sep 9, 2011 at 5:18 PM, Eric Shamow <eric@puppetlabs.com> >> wrote: >> > Notify is a resource, notice() is a function. So notice() is >> > evaluated on the server, whereas notify{} is evaluated on the >> > client. >> > >> > My suspicion is that you somehow have two versions of the client >> > binary hanging around. Perhaps one that is running when you >> > execute "puppet" at the shell, and another running in the >> > background. >> > >> > Per Ken''s question - how are you launching Puppet? Is it as a >> > service? Or are you running it from a cron job? >> >> I know that notice() is a function, and notify{} is a resource. The >> documentation says that much. However, it doesn''t really go beyond >> that. The documentation >> provides examples of how to use notify{} to notify another resource >> when it changes, but I don''t believe it gives you any indication >> whatsoever that you can use it in a stand alone fashion like this. >> Where is that use documented? How would anyone except the core puppet >> developers know that you could even do this? > > I think you are confusing > > server{"foo": notify => Service["bar"]} > > with the resource called notify that you can see documented here: > > http://docs.puppetlabs.com/references/stable/type.html#notify > > >> >> I''m launching puppet with ''service puppet restart''. What libraries? >> If you know their names I can search for them. > > on the node in question, did you perhaps have a puppet installed by > rubygem and then later with rpm/deb, or always only used the one method > and upgraded that using the sameWell, I can''t seem to work out what''s going on. A ''gem list --local'' shows only stomp and I can''t find any other libraries or binaries installed anywhere after removing the puppet and facter RPM''s. :( Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>>> I''m launching puppet with ''service puppet restart''.Do you get any different results if you run it like: puppet agent -t Instead of using that service? Are you absolutely certain there isn''t a stray ruby process running your old 0.25 puppet agent?> Well, I can''t seem to work out what''s going on. A ''gem list --local'' > shows only stomp and I can''t find any other libraries or binaries > installed anywhere after removing the puppet and facter RPM''s. :(Can you post your puppet.conf from your client and server? Are you able to replicate this problem on other nodes? So far we have only discussed a single node. The node we have been discussing was ''upgraded'' from 0.25 to 2.7 wasn''t it? What process did you go through to do the upgrade? I presume this problem doesn''t exist with a brand new node that has 2.7 and has not been upgraded? 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 10:50 AM, Ken Barber <ken@puppetlabs.com> wrote:>>>> I''m launching puppet with ''service puppet restart''. > > Do you get any different results if you run it like: > > puppet agent -twarning: You have configuration parameter $localconfig specified in [puppetd], which is a deprecated section. I''m assuming you meant [agent] warning: You have configuration parameter $classfile specified in [puppetd], which is a deprecated section. I''m assuming you meant [agent] warning: You have configuration parameter $report specified in [puppetd], which is a deprecated section. I''m assuming you meant [agent] info: Retrieving plugin info: Loading facts in release_ver info: Loading facts in lb_status_setup info: Loading facts in release_ver info: Loading facts in lb_status_setup info: Caching catalog for hproxy11.h.foo.com info: Applying configuration version ''1315739532'' notice: 0.25.5 on hproxy11.h.foo.com notice: /Stage[main]/Puppet::Setup/Notify[0.25.5 on hproxy11.h.foo.com]/message: defined ''message'' as ''0.25.5 on hproxy11.h.foo.com'' notice: Finished catalog run in 22.78 seconds> > Instead of using that service? > > Are you absolutely certain there isn''t a stray ruby process running > your old 0.25 puppet agent?[root@hproxy11 ~]# ps -ef | grep ruby root 17832 1 4 10:47 ? 00:00:16 /usr/bin/ruby /usr/sbin/puppetd root 21791 10329 0 10:53 pts/0 00:00:00 grep ruby root 30729 1 0 Sep02 ? 00:00:01 ruby /usr/sbin/mcollectived --pid=/var/run/mcollectived.pid --config=/etc/mcollective/server.cfg> >> Well, I can''t seem to work out what''s going on. A ''gem list --local'' >> shows only stomp and I can''t find any other libraries or binaries >> installed anywhere after removing the puppet and facter RPM''s. :( > > Can you post your puppet.conf from your client and server?From client: # This file is managed by puppet # # Manual changes to this file will get overwritten # [main] # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is ''$vardir/run''. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is ''$confdir/ssl''. ssldir = $vardir/ssl pluginsync = true factpath = $vardir/lib/facter [puppetd] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is ''$confdir/classes.txt''. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is ''$confdir/localconfig''. localconfig = $vardir/localconfig # Enable reports report = true From server: [main] # Where Puppet stores dynamic and growing data. # The default value is ''/var/puppet'' vardir = /var/lib/puppet # The Puppet log directory. # The default value is ''$vardir/log''. logdir = /var/log/puppet # Where Puppet PID files are kept. # The default value is ''$vardir/run''. rundir = /var/run/puppet # Where SSL certificates are kept. # The default value is ''$confdir/ssl''. ssldir = $vardir/ssl external_nodes = /etc/puppet/bin/getnode.sh node_terminus = exec [production] manifest = /etc/puppet/manifests/site.pp modulepath = /etc/puppet/modules [agent] # The file in which puppetd stores a list of the classes # associated with the retrieved configuratiion. Can be loaded in # the separate ``puppet`` executable using the ``--loadclasses`` # option. # The default value is ''$confdir/classes.txt''. classfile = $vardir/classes.txt # Where puppetd caches the local configuration. An # extension indicating the cache format is added automatically. # The default value is ''$confdir/localconfig''. localconfig = $vardir/localconfig [master] # this is because of the shared vip between the 2 puppetmasters certname=puppet autosign=/etc/puppet/autosign.conf # reporting reportdir = /var/lib/puppet/reports/ reports = log,tagmail syslogfacility = local7> > Are you able to replicate this problem on other nodes? So far we have > only discussed a single node.Yes. I am seeing this behaviour on a 2nd node as well.> The node we have been discussing was ''upgraded'' from 0.25 to 2.7 > wasn''t it? What process did you go through to do the upgrade?Correct. On Client: service puppet stop yum clean all rpm --erase puppet rpm --erase facter rm -fR /var/lib/puppet yum upgrade puppet On server: puppetca --clean hproxy11.h.foo.com On Client: service puppet start> > I presume this problem doesn''t exist with a brand new node that has > 2.7 and has not been upgraded?I don''t know. I don''t have access to a fresh 2.7 install on the server right now. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> On Client: > service puppet stop > yum clean all > rpm --erase puppet > rpm --erase facter > rm -fR /var/lib/puppet > yum upgrade puppet > > On server: > puppetca --clean hproxy11.h.foo.com > > On Client: > service puppet startWhere are the RPM''s from that you are using for both 0.25.5 and 2.7.3? I wonder if this can be replicated elsewhere ... what OS distribution and version are you using? I still can''t help but think you have some stray presence of 0.25.5 somewhere. Can you check /usr/local for any traces of Puppet that may have been manually installed at any point? Something like: find /usr/local -name ''*puppet*'' Now the fact gets the puppet version from Puppet::PUPPETVERSION ... so can you grep this from your ruby path? cd /usr/lib/ruby (or lib64?) grep -r ''PUPPETVERSION'' * You should really only get something like: root@node1:/usr/lib/ruby/1.8# grep -r ''PUPPETVERSION'' * 1.8/puppet/face/help/global.erb:Puppet v<%= Puppet::PUPPETVERSION %> 1.8/puppet.rb: PUPPETVERSION = ''2.7.1'' 1.8/puppet.rb: PUPPETVERSION root@node1:/usr/lib/ruby# But obviously 2.7.3 not 2.7.1. Also check your environment variable RUBYLIB: echo $RUBYLIB And show us the result ... repeating the grep for PUPPETVERSION in any path specified there as well. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 11:24 AM, Ken Barber <ken@puppetlabs.com> wrote:>> On Client: >> service puppet stop >> yum clean all >> rpm --erase puppet >> rpm --erase facter >> rm -fR /var/lib/puppet >> yum upgrade puppet >> >> On server: >> puppetca --clean hproxy11.h.foo.com >> >> On Client: >> service puppet start > > Where are the RPM''s from that you are using for both 0.25.5 and 2.7.3? > I wonder if this can be replicated elsewhere ... what OS distribution > and version are you using? > > I still can''t help but think you have some stray presence of 0.25.5 > somewhere. Can you check /usr/local for any traces of Puppet that may > have been manually installed at any point? Something like: > > find /usr/local -name ''*puppet*''service puppet stop rpm --erase puppet rpm --erase facter rm -fR /var/lib/puppet find /usr/local -name "*puppet*" (yeilds nothing)> > Now the fact gets the puppet version from Puppet::PUPPETVERSION ... so > can you grep this from your ruby path? > > cd /usr/lib/ruby (or lib64?) > grep -r ''PUPPETVERSION'' *After reinstalling puppet 2.7.3 again... [root@hproxy11 ruby]# cd /usr/lib64/ruby [root@hproxy11 ruby]# grep -r ''PUPPETVERSION'' * [root@hproxy11 ruby]# cd /usr/lib/ruby [root@hproxy11 ruby]# grep -r ''PUPPETVERSION'' * site_ruby/1.8/facter/puppetversion.rb: Puppet::PUPPETVERSION.to_s site_ruby/1.8/puppet/face/help/global.erb:Puppet v<%= Puppet::PUPPETVERSION %> site_ruby/1.8/puppet.rb: PUPPETVERSION = ''2.7.3'' site_ruby/1.8/puppet.rb: PUPPETVERSION [root@hproxy11 ruby]# Looks like 2.7.3...> > You should really only get something like: > > root@node1:/usr/lib/ruby/1.8# grep -r ''PUPPETVERSION'' * > 1.8/puppet/face/help/global.erb:Puppet v<%= Puppet::PUPPETVERSION %> > 1.8/puppet.rb: PUPPETVERSION = ''2.7.1'' > 1.8/puppet.rb: PUPPETVERSION > root@node1:/usr/lib/ruby# > > But obviously 2.7.3 not 2.7.1. Also check your environment variable RUBYLIB: > > echo $RUBYLIB[root@hproxy11 ruby]# echo $RUBYLIB [root@hproxy11 ruby]#> > And show us the result ... repeating the grep for PUPPETVERSION in any > path specified there as well.Since RUBYLIB was empty... Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
>> Where are the RPM''s from that you are using for both 0.25.5 and 2.7.3? >> I wonder if this can be replicated elsewhere ... what OS distribution >> and version are you using?If you can let me know this info I can probably try to replicate. One thing was troubling me ... and its probably a long shot. (I''m not even certain its possible). I notice you had a fact called ''release_ver'' being synced ... can you confirm there is no overlap anywhere with puppetversion? Do something like: grep -r ''puppetversion'' /var/lib/puppet/ Maybe even try clearing /var/lib/puppet/lib and disabling pluginsync on the client just for kicks. Also my puppet version looks something like this - can you confirm it looks the same: Facter.add(:puppetversion) do setcode do begin require ''puppet'' Puppet::PUPPETVERSION.to_s rescue LoadError nil end end end Its in /usr/lib/ruby/vendor_ruby/facter/puppetversion.rb ... but probably different on centos or whatever. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 12:35 PM, Ken Barber <ken@puppetlabs.com> wrote:>>> Where are the RPM''s from that you are using for both 0.25.5 and 2.7.3? >>> I wonder if this can be replicated elsewhere ... what OS distribution >>> and version are you using? > > If you can let me know this info I can probably try to replicate.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 because Puppet Labs seems to think it''s not their job to maintain this file. I''ll probably get in trouble for saying that.> > One thing was troubling me ... and its probably a long shot. (I''m not > even certain its possible). > > I notice you had a fact called ''release_ver'' being synced ... can you > confirm there is no overlap anywhere with puppetversion?The release_ver fact sets version information on our proprietary application. It''s got stuff like this: # Test if the symlink exists for the lb_status module Facter.add("current-diffd") do setcode do target = File.readlink("/var/foo/releases/current-diffd") target end end No mention of the puppet version.> > Do something like: > > grep -r ''puppetversion'' /var/lib/puppet/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?> > Maybe even try clearing /var/lib/puppet/lib and disabling pluginsync > on the client just for kicks.I''ve been blowing away /var/lib/puppet when I remove the RPM before installing the new one.> > Also my puppet version looks something like this - can you confirm it > looks the same: > > Facter.add(:puppetversion) do > setcode do > begin > require ''puppet'' > Puppet::PUPPETVERSION.to_s > rescue LoadError > nil > end > end > end > > Its in /usr/lib/ruby/vendor_ruby/facter/puppetversion.rb ... but > probably different on centos or whatever. ># Fact: puppetversion # # Purpose: Return the version of puppet installed. # # Resolution: # Requres puppet via Ruby and returns it''s version constant. # # Caveats: # /usr/lib/ruby/site_ruby/1.8/facter/puppetversion.rb: Facter.add(:puppetversion) do setcode do begin require ''puppet'' Puppet::PUPPETVERSION.to_s rescue LoadError nil end end end -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 1:08 PM, Ken Barber <ken@puppetlabs.com> wrote:>> 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?O/S on server is CentOS 5.4. O/S on client(s) is CentOS 5.5 I answered this one in the previous message, but I got the source from Puppet Labs, modified the RPM spec file to make it work, and built the RPM''s from that,.> > Also ... why don''t you try these RPM''s for 2.7.x: > > http://yum.puppetlabs.com/el/5/productsWell, didn''t know that existed. Maybe due to lack of documentation. Every time I''ve complained about the spec files not being maintained in the source code, Puppet labs people have said it wasn''t their job to maintain the spec file. Given that there are pre-build RPM''s on the puppet labs web site, I guess it''s someone''s job to maintain the spec file.> > I think Mike just updated these.I''ll give the client a try first. Little more worried about updating the server.> >> 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.Thanks. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 1:17 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Mon, Sep 12, 2011 at 1:08 PM, Ken Barber <ken@puppetlabs.com> wrote: >>> 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? > > O/S on server is CentOS 5.4. O/S on client(s) is CentOS 5.5 > > I answered this one in the previous message, but I got the source from > Puppet Labs, modified the RPM spec file to make it work, and built the > RPM''s from that,. > >> >> Also ... why don''t you try these RPM''s for 2.7.x: >> >> http://yum.puppetlabs.com/el/5/products > > Well, didn''t know that existed. Maybe due to lack of documentation. > Every time I''ve complained about the spec files not being maintained > in the source code, Puppet labs people have said it wasn''t their job > to maintain the spec file. Given that there are pre-build RPM''s on the > puppet labs web site, I guess it''s someone''s job to maintain the spec > file. > >> >> I think Mike just updated these. > > I''ll give the client a try first. Little more worried about updating the server.Uhm... what am I missing here? [root@hproxy11 tmp]# rpm -i facter-1.6.0-1.x86_64.rpm error: facter-1.6.0-1.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 4bd6ec30 error: facter-1.6.0-1.x86_64.rpm cannot be installed [root@hproxy11 tmp]# rpm -i puppet-2.7.3-1.el5.noarch.rpm error: puppet-2.7.3-1.el5.noarch.rpm: Header V4 RSA/SHA1 signature: BAD, key ID 4bd6ec30 error: puppet-2.7.3-1.el5.noarch.rpm cannot be installed Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
You haven''t imported the public key for that repository. Ken was probably assuming that you''d add the repo to your list of repositories and use yum to install. If you aren''t going to do that, you need the GPG key: RPM-GPG-KEY-puppetlabs (http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs) -Eric -- Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 23rd in Portland, OR. Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Monday, September 12, 2011 at 4:25 PM, Douglas Garstang wrote:> On Mon, Sep 12, 2011 at 1:17 PM, Douglas Garstang > <doug.garstang@gmail.com (mailto:doug.garstang@gmail.com)> wrote: > > On Mon, Sep 12, 2011 at 1:08 PM, Ken Barber <ken@puppetlabs.com (mailto:ken@puppetlabs.com)> wrote: > > > > 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? > > > > O/S on server is CentOS 5.4. O/S on client(s) is CentOS 5.5 > > > > I answered this one in the previous message, but I got the source from > > Puppet Labs, modified the RPM spec file to make it work, and built the > > RPM''s from that,. > > > > > > > > Also ... why don''t you try these RPM''s for 2.7.x: > > > > > > http://yum.puppetlabs.com/el/5/products > > > > Well, didn''t know that existed. Maybe due to lack of documentation. > > Every time I''ve complained about the spec files not being maintained > > in the source code, Puppet labs people have said it wasn''t their job > > to maintain the spec file. Given that there are pre-build RPM''s on the > > puppet labs web site, I guess it''s someone''s job to maintain the spec > > file. > > > > > > > > I think Mike just updated these. > > > > I''ll give the client a try first. Little more worried about updating the server. > > Uhm... what am I missing here? > > [root@hproxy11 tmp]# rpm -i facter-1.6.0-1.x86_64.rpm > error: facter-1.6.0-1.x86_64.rpm: Header V4 RSA/SHA1 signature: BAD, > key ID 4bd6ec30 > error: facter-1.6.0-1.x86_64.rpm cannot be installed > > [root@hproxy11 tmp]# rpm -i puppet-2.7.3-1.el5.noarch.rpm > error: puppet-2.7.3-1.el5.noarch.rpm: Header V4 RSA/SHA1 signature: > BAD, key ID 4bd6ec30 > error: puppet-2.7.3-1.el5.noarch.rpm cannot be installed > > Doug > > -- > 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 (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto:puppet-users+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 1:28 PM, Eric Shamow <eric@puppetlabs.com> wrote:> You haven''t imported the public key for that repository. Ken was probably assuming that you''d add the repo to your list of repositories and use yum to install. If you aren''t going to do that, you need the GPG key: > > RPM-GPG-KEY-puppetlabs (http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs) > > -EricWeird, I installed the key in /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs, did an rpm --import, and I''m still getting the error. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 1:41 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Mon, Sep 12, 2011 at 1:28 PM, Eric Shamow <eric@puppetlabs.com> wrote: >> You haven''t imported the public key for that repository. Ken was probably assuming that you''d add the repo to your list of repositories and use yum to install. If you aren''t going to do that, you need the GPG key: >> >> RPM-GPG-KEY-puppetlabs (http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs) >> >> -Eric > > Weird, I installed the key in /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs, > did an rpm --import, and I''m still getting the error.So, I managed to install those RPM''s (puppet and facter) on the client, and got the same results. Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas, This is a long shot, but if you have your locate database being updated nightly, as is the default for RH-based OSes, can you run "locate puppet | pbcopy" and paste the results into a pastebin/pastie/your paste of choice? I''d like to see where this shows up on your system. I think there really are remnants of an earlier install hanging around. -Eric -- Join us for PuppetConf (http://www.bit.ly/puppetconfsig), September 22nd and 23rd in Portland, OR. Eric Shamow Professional Services http://puppetlabs.com/ (c)631.871.6441 On Monday, September 12, 2011 at 6:07 PM, Douglas Garstang wrote:> On Mon, Sep 12, 2011 at 1:41 PM, Douglas Garstang > <doug.garstang@gmail.com (mailto:doug.garstang@gmail.com)> wrote: > > On Mon, Sep 12, 2011 at 1:28 PM, Eric Shamow <eric@puppetlabs.com (mailto:eric@puppetlabs.com)> wrote: > > > You haven''t imported the public key for that repository. Ken was probably assuming that you''d add the repo to your list of repositories and use yum to install. If you aren''t going to do that, you need the GPG key: > > > > > > RPM-GPG-KEY-puppetlabs (http://yum.puppetlabs.com/RPM-GPG-KEY-puppetlabs) > > > > > > -Eric > > > > Weird, I installed the key in /etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs, > > did an rpm --import, and I''m still getting the error. > > So, I managed to install those RPM''s (puppet and facter) on the > client, and got the same results. > > Doug > > -- > 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 (mailto:puppet-users@googlegroups.com). > To unsubscribe from this group, send email to puppet-users+unsubscribe@googlegroups.com (mailto:puppet-users+unsubscribe@googlegroups.com). > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Mon, Sep 12, 2011 at 3:28 PM, Eric Shamow <eric@puppetlabs.com> wrote:> Douglas, > > This is a long shot, but if you have your locate database being updated nightly, as is the default for RH-based OSes, can you run "locate puppet | pbcopy" and paste the results into a pastebin/pastie/your paste of choice?I don''t know what pbcopy is.... locate can''t find it. Never heard of it, but, after removing the rpm and wiping /var/lib/puppet and running ''locate puppet'', I get: [root@hproxy11 ~]# locate puppet /etc/puppet /etc/logrotate.d/puppet /etc/puppet/auth.conf /etc/puppet/puppet.conf /etc/rc.d/init.d/puppet /etc/rc.d/rc0.d/K02puppet /etc/rc.d/rc1.d/K02puppet /etc/rc.d/rc2.d/S98puppet /etc/rc.d/rc3.d/S98puppet /etc/rc.d/rc4.d/S98puppet /etc/rc.d/rc5.d/S98puppet /etc/rc.d/rc6.d/K02puppet /etc/sysconfig/puppet /usr/bin/mc-puppetd /usr/bin/puppet /usr/bin/puppetdoc /usr/lib/ruby/site_ruby/1.8/puppet /usr/lib/ruby/site_ruby/1.8/puppet.rb /usr/lib/ruby/site_ruby/1.8/facter/puppetversion.rb /usr/lib/ruby/site_ruby/1.8/puppet/agent /usr/lib/ruby/site_ruby/1.8/puppet/agent.rb /usr/lib/ruby/site_ruby/1.8/puppet/application /usr/lib/ruby/site_ruby/1.8/puppet/application.rb /usr/lib/ruby/site_ruby/1.8/puppet/checksum.rb /usr/lib/ruby/site_ruby/1.8/puppet/configurer /usr/lib/ruby/site_ruby/1.8/puppet/configurer.rb /usr/lib/ruby/site_ruby/1.8/puppet/daemon.rb /usr/lib/ruby/site_ruby/1.8/puppet/defaults.rb /usr/lib/ruby/site_ruby/1.8/puppet/dsl.rb /usr/lib/ruby/site_ruby/1.8/puppet/error.rb /usr/lib/ruby/site_ruby/1.8/puppet/external /usr/lib/ruby/site_ruby/1.8/puppet/feature /usr/lib/ruby/site_ruby/1.8/puppet/file_collection /usr/lib/ruby/site_ruby/1.8/puppet/file_collection.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving /usr/lib/ruby/site_ruby/1.8/puppet/file_serving.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector /usr/lib/ruby/site_ruby/1.8/puppet/indirector.rb /usr/lib/ruby/site_ruby/1.8/puppet/metatype /usr/lib/ruby/site_ruby/1.8/puppet/module.rb /usr/lib/ruby/site_ruby/1.8/puppet/network /usr/lib/ruby/site_ruby/1.8/puppet/network.rb /usr/lib/ruby/site_ruby/1.8/puppet/node /usr/lib/ruby/site_ruby/1.8/puppet/node.rb /usr/lib/ruby/site_ruby/1.8/puppet/parameter.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser /usr/lib/ruby/site_ruby/1.8/puppet/property /usr/lib/ruby/site_ruby/1.8/puppet/property.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider /usr/lib/ruby/site_ruby/1.8/puppet/provider.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails /usr/lib/ruby/site_ruby/1.8/puppet/rails.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference /usr/lib/ruby/site_ruby/1.8/puppet/relationship.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports /usr/lib/ruby/site_ruby/1.8/puppet/reports.rb /usr/lib/ruby/site_ruby/1.8/puppet/resource /usr/lib/ruby/site_ruby/1.8/puppet/resource.rb /usr/lib/ruby/site_ruby/1.8/puppet/simple_graph.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl /usr/lib/ruby/site_ruby/1.8/puppet/ssl.rb /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates.rb /usr/lib/ruby/site_ruby/1.8/puppet/transaction /usr/lib/ruby/site_ruby/1.8/puppet/transaction.rb /usr/lib/ruby/site_ruby/1.8/puppet/transportable.rb /usr/lib/ruby/site_ruby/1.8/puppet/type /usr/lib/ruby/site_ruby/1.8/puppet/type.rb /usr/lib/ruby/site_ruby/1.8/puppet/util /usr/lib/ruby/site_ruby/1.8/puppet/util.rb /usr/lib/ruby/site_ruby/1.8/puppet/agent/locker.rb /usr/lib/ruby/site_ruby/1.8/puppet/agent/runner.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/filebucket.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/pi.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppet.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetca.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetd.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetdoc.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetmasterd.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetqd.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/puppetrun.rb /usr/lib/ruby/site_ruby/1.8/puppet/application/ralsh.rb /usr/lib/ruby/site_ruby/1.8/puppet/configurer/downloader.rb /usr/lib/ruby/site_ruby/1.8/puppet/configurer/fact_handler.rb /usr/lib/ruby/site_ruby/1.8/puppet/configurer/plugin_handler.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/base64.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/dot.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/lock.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/nagios /usr/lib/ruby/site_ruby/1.8/puppet/external/nagios.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/pson /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/better-definers.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/event-loop.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/event-loop/signal-system.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/nagios/base.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/nagios/parser.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/pson/common.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/pson/pure /usr/lib/ruby/site_ruby/1.8/puppet/external/pson/pure.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/pson/version.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/pson/pure/generator.rb /usr/lib/ruby/site_ruby/1.8/puppet/external/pson/pure/parser.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/base.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/pson.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/rack.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/rails.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/rubygems.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/selinux.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/stomp.rb /usr/lib/ruby/site_ruby/1.8/puppet/feature/zlib.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_collection/lookup.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/base.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/configuration /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/configuration.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/content.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/fileset.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/indirection_hooks.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/metadata.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/mount /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/mount.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/terminus_helper.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/configuration/parser.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/mount/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/mount/modules.rb /usr/lib/ruby/site_ruby/1.8/puppet/file_serving/mount/plugins.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/active_record.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_request /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_revocation_list /usr/lib/ruby/site_ruby/1.8/puppet/indirector/checksum /usr/lib/ruby/site_ruby/1.8/puppet/indirector/code.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/direct_file_server.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/envelope.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/exec.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_content /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_content.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_metadata /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_metadata.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_server.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/indirection.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/key /usr/lib/ruby/site_ruby/1.8/puppet/indirector/ldap.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/memory.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node /usr/lib/ruby/site_ruby/1.8/puppet/indirector/plain.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/queue.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/report /usr/lib/ruby/site_ruby/1.8/puppet/indirector/request.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/runner /usr/lib/ruby/site_ruby/1.8/puppet/indirector/ssl_file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/terminus.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/yaml.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/active_record.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/compiler.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/queue.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/catalog/yaml.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_request/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_request/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_request/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_revocation_list/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_revocation_list/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/certificate_revocation_list/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/active_record.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/facter.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/memory.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/facts/yaml.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_content/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_content/file_server.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_content/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_metadata/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_metadata/file_server.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/file_metadata/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/key/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/key/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/active_record.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/exec.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/ldap.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/memory.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/plain.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/node/yaml.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/report/processor.rb /usr/lib/ruby/site_ruby/1.8/puppet/indirector/report/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/metatype/manager.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/authconfig.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/authorization.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/authstore.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client /usr/lib/ruby/site_ruby/1.8/puppet/network/client.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client_request.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/format.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/format_handler.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/formats.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler /usr/lib/ruby/site_ruby/1.8/puppet/network/handler.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http /usr/lib/ruby/site_ruby/1.8/puppet/network/http.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http_pool.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http_server /usr/lib/ruby/site_ruby/1.8/puppet/network/http_server.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/rest_authconfig.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/rest_authorization.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/rest_controller.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/rights.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/server.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc /usr/lib/ruby/site_ruby/1.8/puppet/network/client/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/dipper.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/proxy.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/report.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/resource.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/runner.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/client/status.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/filebucket.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/fileserver.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/master.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/report.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/resource.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/runner.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/handler/status.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/api /usr/lib/ruby/site_ruby/1.8/puppet/network/http/api.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/handler.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/mongrel /usr/lib/ruby/site_ruby/1.8/puppet/network/http/mongrel.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/api/v1.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/mongrel/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack/httphandler.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/rack/xmlrpc.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http/webrick/rest.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http_server/mongrel.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/http_server/webrick.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/client.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/processor.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/server.rb /usr/lib/ruby/site_ruby/1.8/puppet/network/xmlrpc/webrick_servlet.rb /usr/lib/ruby/site_ruby/1.8/puppet/node/environment.rb /usr/lib/ruby/site_ruby/1.8/puppet/node/facts.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/collector.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/compiler.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/files.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/interpreter.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/lexer.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/loaded_code.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/parser_support.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/resource /usr/lib/ruby/site_ruby/1.8/puppet/parser/resource.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/scope.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/templatewrapper.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/yaml_trimmer.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/arithmetic_operator.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/astarray.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/boolean_operator.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/branch.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/caseopt.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/casestatement.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/collection.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/collexpr.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/comparison_operator.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/definition.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/else.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/function.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/hostclass.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/ifstatement.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/leaf.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/match_operator.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/minus.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/node.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/nop.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/not.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resource.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resource_defaults.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resource_override.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resource_reference.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/resourceparam.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/selector.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/tag.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/ast/vardef.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/defined.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/fail.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/fqdn_rand.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/generate.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/include.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/inline_template.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/realize.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/regsubst.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/require.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/search.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/sha1.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/shellquote.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/split.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/sprintf.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/tag.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/tagged.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/template.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/functions/versioncmp.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/resource/param.rb /usr/lib/ruby/site_ruby/1.8/puppet/parser/resource/reference.rb /usr/lib/ruby/site_ruby/1.8/puppet/property/keyvalue.rb /usr/lib/ruby/site_ruby/1.8/puppet/property/list.rb /usr/lib/ruby/site_ruby/1.8/puppet/property/ordered_list.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/augeas /usr/lib/ruby/site_ruby/1.8/puppet/provider/computer /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine_collection.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confiner.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/cron /usr/lib/ruby/site_ruby/1.8/puppet/provider/group /usr/lib/ruby/site_ruby/1.8/puppet/provider/host /usr/lib/ruby/site_ruby/1.8/puppet/provider/ldap.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/macauthorization /usr/lib/ruby/site_ruby/1.8/puppet/provider/mailalias /usr/lib/ruby/site_ruby/1.8/puppet/provider/maillist /usr/lib/ruby/site_ruby/1.8/puppet/provider/mcx /usr/lib/ruby/site_ruby/1.8/puppet/provider/mount /usr/lib/ruby/site_ruby/1.8/puppet/provider/mount.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/naginator.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/nameservice /usr/lib/ruby/site_ruby/1.8/puppet/provider/nameservice.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package /usr/lib/ruby/site_ruby/1.8/puppet/provider/package.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/parsedfile.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/port /usr/lib/ruby/site_ruby/1.8/puppet/provider/selboolean /usr/lib/ruby/site_ruby/1.8/puppet/provider/selmodule /usr/lib/ruby/site_ruby/1.8/puppet/provider/service /usr/lib/ruby/site_ruby/1.8/puppet/provider/ssh_authorized_key /usr/lib/ruby/site_ruby/1.8/puppet/provider/sshkey /usr/lib/ruby/site_ruby/1.8/puppet/provider/user /usr/lib/ruby/site_ruby/1.8/puppet/provider/zfs /usr/lib/ruby/site_ruby/1.8/puppet/provider/zone /usr/lib/ruby/site_ruby/1.8/puppet/provider/zpool /usr/lib/ruby/site_ruby/1.8/puppet/provider/augeas/augeas.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/computer/computer.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine/exists.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine/false.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine/feature.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine/true.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/confine/variable.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/cron/crontab.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/group/directoryservice.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/group/groupadd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/group/ldap.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/group/pw.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/host/parsed.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/macauthorization/macauthorization.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/mailalias/aliases.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/maillist/mailman.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/mcx/mcxcontent.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/mount/parsed.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/nameservice/directoryservice.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/nameservice/objectadd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/nameservice/pw.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/appdmg.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/apple.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/apt.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/aptitude.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/aptrpm.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/blastwave.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/darwinport.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/dpkg.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/fink.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/freebsd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/gem.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/hpux.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/openbsd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/pkgdmg.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/portage.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/ports.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/rpm.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/rug.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/sun.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/sunfreeware.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/up2date.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/urpmi.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yum.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.py /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.pyc /usr/lib/ruby/site_ruby/1.8/puppet/provider/package/yumhelper.pyo /usr/lib/ruby/site_ruby/1.8/puppet/provider/port/parsed.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/selboolean/getsetsebool.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/selmodule/semodule.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/base.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/daemontools.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/debian.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/freebsd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/gentoo.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/init.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/launchd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/redhat.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/runit.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/service/smf.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/ssh_authorized_key/parsed.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/sshkey/parsed.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/directoryservice.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/hpux.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/ldap.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/pw.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/user_role_add.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/user/useradd.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/zfs/solaris.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/zone/solaris.rb /usr/lib/ruby/site_ruby/1.8/puppet/provider/zpool/solaris.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/benchmark.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/database /usr/lib/ruby/site_ruby/1.8/puppet/rails/fact_name.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/fact_value.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/host.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_name.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/param_value.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/puppet_tag.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/resource.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/resource_tag.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/source_file.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/database/001_add_created_at_to_all_tables.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/database/002_remove_duplicated_index_on_all_tables.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/database/003_add_environment_to_host.rb /usr/lib/ruby/site_ruby/1.8/puppet/rails/database/schema.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/configuration.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/function.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/indirection.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/metaparameter.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/network.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/providers.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/report.rb /usr/lib/ruby/site_ruby/1.8/puppet/reference/type.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports/log.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports/rrdgraph.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports/store.rb /usr/lib/ruby/site_ruby/1.8/puppet/reports/tagmail.rb /usr/lib/ruby/site_ruby/1.8/puppet/resource/catalog.rb /usr/lib/ruby/site_ruby/1.8/puppet/resource/reference.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/base.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_factory.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_request.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_revocation_list.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/host.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/inventory.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/key.rb /usr/lib/ruby/site_ruby/1.8/puppet/ssl/certificate_authority/interface.rb /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates/ca.rb /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates/certificate.rb /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates/inventory.rb /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates/monkey_patch.rb /usr/lib/ruby/site_ruby/1.8/puppet/sslcertificates/support.rb /usr/lib/ruby/site_ruby/1.8/puppet/transaction/change.rb /usr/lib/ruby/site_ruby/1.8/puppet/transaction/event.rb /usr/lib/ruby/site_ruby/1.8/puppet/transaction/report.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/augeas.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/component.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/computer.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/cron.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/exec.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file /usr/lib/ruby/site_ruby/1.8/puppet/type/file.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/filebucket.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/group.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/host.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/k5login.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/macauthorization.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/mailalias.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/maillist.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/mcx.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/mount.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_command.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_contact.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_contactgroup.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_host.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_hostdependency.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_hostescalation.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_hostextinfo.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_hostgroup.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_service.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_servicedependency.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_serviceescalation.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_serviceextinfo.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_servicegroup.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/nagios_timeperiod.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/notify.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/package.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/port.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/resources.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/schedule.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/selboolean.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/selmodule.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/service.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/ssh_authorized_key.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/sshkey.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/tidy.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/user.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/yumrepo.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/zfs.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/zone.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/zpool.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/checksum.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/content.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/ensure.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/group.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/mode.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/owner.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/selcontext.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/source.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/target.rb /usr/lib/ruby/site_ruby/1.8/puppet/type/file/type.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/autoload /usr/lib/ruby/site_ruby/1.8/puppet/util/autoload.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/backups.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/cacher.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/checksums.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/classgen.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/config_store.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/constant_inflector.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/diff.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/docs.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/errors.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/execution.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/feature.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/file_locking.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/fileparsing.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/filetype.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/graph.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/inifile.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/instance_loader.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/ldap /usr/lib/ruby/site_ruby/1.8/puppet/util/ldap.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/loadedfile.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/log.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/log_paths.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/logging.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/metaid.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/methodhelper.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/metric.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/monkey_patches.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/nagios_maker.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/package.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/pidlock.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/posix.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/provider_features.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/pson.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/queue /usr/lib/ruby/site_ruby/1.8/puppet/util/queue.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rails /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/reference.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/resource_template.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/selinux.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/settings /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/storage.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/subclass_loader.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/suidmanager.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/tagging.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/user_attr.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/warnings.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/zaml.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/autoload/file_cache.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/ldap/connection.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/ldap/generator.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/ldap/manager.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/queue/stomp.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rails/cache_accumulator.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rails/collection_merger.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rails/reference_serializer.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/code_objects.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/generators /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/parser.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/generators/puppet_generator.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/generators/template /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/generators/template/puppet /usr/lib/ruby/site_ruby/1.8/puppet/util/rdoc/generators/template/puppet/puppet.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/settings/boolean_setting.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/settings/file_setting.rb /usr/lib/ruby/site_ruby/1.8/puppet/util/settings/setting.rb /usr/lib64/nagios/plugins/check_puppet.pl /usr/libexec/mcollective/mcollective/agent/puppet-package.rb /usr/libexec/mcollective/mcollective/agent/puppet-service.rb /usr/libexec/mcollective/mcollective/agent/puppetca.ddl /usr/libexec/mcollective/mcollective/agent/puppetca.rb /usr/libexec/mcollective/mcollective/agent/puppetd.ddl /usr/libexec/mcollective/mcollective/agent/puppetd.rb /usr/libexec/mcollective/mcollective/agent/puppetral.rb /usr/sbin/puppetca /usr/sbin/puppetd /usr/share/puppet /usr/share/augeas/lenses/dist/puppet.aug /usr/share/augeas/lenses/dist/tests/test_puppet.aug /usr/share/doc/puppet-0.25.5 /usr/share/emacs/site-lisp/puppet-mode.el /usr/share/emacs/site-lisp/site-start.d/puppet-mode-init.el /usr/share/man/man5/puppet.conf.5.gz /usr/share/man/man8/puppet.8.gz /usr/share/man/man8/puppetca.8.gz /usr/share/man/man8/puppetd.8.gz /usr/share/man/man8/puppetdoc.8.gz /usr/share/puppet/ext /usr/share/puppet/ext/autotest /usr/share/puppet/ext/dbfix.sql /usr/share/puppet/ext/extlookup.rb /usr/share/puppet/ext/ldap /usr/share/puppet/ext/logcheck /usr/share/puppet/ext/nagios /usr/share/puppet/ext/puppet-test /usr/share/puppet/ext/puppetlast /usr/share/puppet/ext/puppetlisten /usr/share/puppet/ext/puppetstoredconfigclean.rb /usr/share/puppet/ext/rack /usr/share/puppet/ext/regexp_nodes /usr/share/puppet/ext/autotest/Rakefile /usr/share/puppet/ext/autotest/config /usr/share/puppet/ext/autotest/readme.rst /usr/share/puppet/ext/ldap/puppet.schema /usr/share/puppet/ext/logcheck/puppet /usr/share/puppet/ext/nagios/check_puppet.rb /usr/share/puppet/ext/nagios/naggen /usr/share/puppet/ext/puppetlisten/puppetlisten.rb /usr/share/puppet/ext/puppetlisten/puppetrun.rb /usr/share/puppet/ext/rack/README /usr/share/puppet/ext/rack/files /usr/share/puppet/ext/rack/manifest.pp /usr/share/puppet/ext/rack/files/apache2.conf /usr/share/puppet/ext/rack/files/config.ru /usr/share/puppet/ext/regexp_nodes/classes /usr/share/puppet/ext/regexp_nodes/parameters /usr/share/puppet/ext/regexp_nodes/regexp_nodes.rb /usr/share/puppet/ext/regexp_nodes/classes/databases /usr/share/puppet/ext/regexp_nodes/classes/webservers /usr/share/puppet/ext/regexp_nodes/parameters/environment /usr/share/puppet/ext/regexp_nodes/parameters/environment/prod /usr/share/puppet/ext/regexp_nodes/parameters/environment/qa /usr/share/vim/vimfiles/ftdetect/puppet.vim /usr/share/vim/vimfiles/syntax/puppet.vim /var/lib/puppet /var/lock/subsys/puppet /var/log/puppet /var/run/puppet /var/run/puppet/puppetd.pid Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Err, what is that 0.25-5 doc folder and what RPM owns it? rpm -qf /usr/share/doc/puppet-0.25.5 If nothing owns it, you''ve pretty much proved your system has old Puppet artefacts lying around. Personally I wouldn''t trust any of the content in /usr/lib/ruby now. Is this a production system? Anything else use Ruby on it? I''d start to get heavy handed as this point: tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) yum remove ruby puppet facter (remove all your RPMs) find /usr/lib/ruby (what''s left in your Ruby libdir?) locate puppet (again, what''s left over, should be almost nothing but / var/lib/puppet, /var/run stuff and config files) Now you could try reinstall and compare your backed up version of /usr/ lib/ruby with your new one. On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> wrote:> [root@hproxy11 ~]# locate puppet...> /usr/share/doc/puppet-0.25.5-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> I don''t know what pbcopy is.... locate can''t find it. Never heard of > it,Yeah never mind - its a convenient Mac OS X tool for copying something into the clipboard. Not critical.> but, after removing the rpm and wiping /var/lib/puppet and running > ''locate puppet'', I get:(you really should use pastie.org for such a large output - its bad netiquette to paste large text onto a mailing list :-). Now I believe locate gets its info from a database, so a lot of this information is going to be old anyway. Just to be sure - can you actually look in /usr/lib/ruby/site_ruby/1.8/puppet/ to make sure its empty after RPM removal? I don''t know about anyone else but I''m running out of ideas. Can you paste (which by that I mean pastie.org) the output of rpm -qlp puppet on your 0.25.5 boxes? I''d be very tempted to see the contents of the srpm/rpm for this. There was one thought I had last night ... and its a long shot. Going back to your initial statement:> After doing that, I''m using the $puppetversion facter variable to determine what version of puppet the client hasCan you show us the exact code for this? I just had a wary feeling about perhaps the way you were doing the expression. If that doesn''t help ... can you run puppet on one of this boxes against a completely empty site.pp ... creating a new environment would probably be the cleanest way of doing this. Make sure the site.pp only has the notify: notify { "Version: ${puppetversion} FQDN: ${fqdn}": } Then show us the result of running: puppet agent -t --environment myenv 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 17:43 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> wrote:> Err, what is that 0.25-5 doc folder and what RPM owns it? > > rpm -qf /usr/share/doc/puppet-0.25.5 > > If nothing owns it, you''ve pretty much proved your system has old > Puppet artefacts lying around. Personally I wouldn''t trust any of the > content in /usr/lib/ruby now. Is this a production system? Anything > else use Ruby on it? > > I''d start to get heavy handed as this point: > > tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) > yum remove ruby puppet facter (remove all your RPMs) > find /usr/lib/ruby (what''s left in your Ruby libdir?) > locate puppet (again, what''s left over, should be almost nothing but / > var/lib/puppet, /var/run stuff and config files) > > Now you could try reinstall and compare your backed up version of /usr/ > lib/ruby with your new one. > > On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> wrote: > >> [root@hproxy11 ~]# locate puppet > ... >> /usr/share/doc/puppet-0.25.5So... this doesn''t make sense. I just did this on the client: rpm --erase puppet rpm --erase facter find / -name "*facter*" -exec rm -rf {} \; find / -name "*puppet*" -exec rm -rf {} \; And then reinstalled puppet and facter, cleaned the certs etc, and restarted puppet. Problem persists... Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
----- Original Message -----> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> > wrote: > > Err, what is that 0.25-5 doc folder and what RPM owns it? > > > > rpm -qf /usr/share/doc/puppet-0.25.5 > > > > If nothing owns it, you''ve pretty much proved your system has old > > Puppet artefacts lying around. Personally I wouldn''t trust any of > > the > > content in /usr/lib/ruby now. Is this a production system? Anything > > else use Ruby on it? > > > > I''d start to get heavy handed as this point: > > > > tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) > > yum remove ruby puppet facter (remove all your RPMs) > > find /usr/lib/ruby (what''s left in your Ruby libdir?) > > locate puppet (again, what''s left over, should be almost nothing > > but / > > var/lib/puppet, /var/run stuff and config files) > > > > Now you could try reinstall and compare your backed up version of > > /usr/ > > lib/ruby with your new one. > > > > On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> > > wrote: > > > >> [root@hproxy11 ~]# locate puppet > > ... > >> /usr/share/doc/puppet-0.25.5 > > So... this doesn''t make sense. > > I just did this on the client: > > rpm --erase puppet > rpm --erase facter > find / -name "*facter*" -exec rm -rf {} \; > find / -name "*puppet*" -exec rm -rf {} \; > > And then reinstalled puppet and facter, cleaned the certs etc, and > restarted puppet. > > Problem persists...maybe these rogue files didnt come from rpm? then it wouldnt know to remove them. Given how much time has been spent on this, I think you should try and install a blank from scratch centos box and install the rpms on it and see how that rolls. -- R.I.Pienaar -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 17:48 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar <rip@devco.net> wrote:> > > ----- Original Message ----- >> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> >> wrote: >> > Err, what is that 0.25-5 doc folder and what RPM owns it? >> > >> > rpm -qf /usr/share/doc/puppet-0.25.5 >> > >> > If nothing owns it, you''ve pretty much proved your system has old >> > Puppet artefacts lying around. Personally I wouldn''t trust any of >> > the >> > content in /usr/lib/ruby now. Is this a production system? Anything >> > else use Ruby on it? >> > >> > I''d start to get heavy handed as this point: >> > >> > tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) >> > yum remove ruby puppet facter (remove all your RPMs) >> > find /usr/lib/ruby (what''s left in your Ruby libdir?) >> > locate puppet (again, what''s left over, should be almost nothing >> > but / >> > var/lib/puppet, /var/run stuff and config files) >> > >> > Now you could try reinstall and compare your backed up version of >> > /usr/ >> > lib/ruby with your new one. >> > >> > On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> >> > wrote: >> > >> >> [root@hproxy11 ~]# locate puppet >> > ... >> >> /usr/share/doc/puppet-0.25.5 >> >> So... this doesn''t make sense. >> >> I just did this on the client: >> >> rpm --erase puppet >> rpm --erase facter >> find / -name "*facter*" -exec rm -rf {} \; >> find / -name "*puppet*" -exec rm -rf {} \; >> >> And then reinstalled puppet and facter, cleaned the certs etc, and >> restarted puppet. >> >> Problem persists... > > maybe these rogue files didnt come from rpm? then it wouldnt know to remove > them.Maybe not, but I''m sure the rm -fR would have taken care of any that weren''t, no? I think we all know that installing puppet 2.7.3 from RPM''s isn''t an issue, or else everyone would be experiencing the same problem. It seems at this point, the problem may lie somewhere on the server, especially as facter locally reports the right value. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Yeah this doesn''t seem to be old versions of Puppet. So from my other email ... can you show us the code where you are doing your comparison for $puppetversion? I have a feeling I might know what it is ... although I''m probably wrong ... In fact - grep for ''puppetversion'' in all of your puppet code ... I''m curious :-). ken. On Tue, Sep 13, 2011 at 6:48 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar <rip@devco.net> wrote: >> >> >> ----- Original Message ----- >>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> >>> wrote: >>> > Err, what is that 0.25-5 doc folder and what RPM owns it? >>> > >>> > rpm -qf /usr/share/doc/puppet-0.25.5 >>> > >>> > If nothing owns it, you''ve pretty much proved your system has old >>> > Puppet artefacts lying around. Personally I wouldn''t trust any of >>> > the >>> > content in /usr/lib/ruby now. Is this a production system? Anything >>> > else use Ruby on it? >>> > >>> > I''d start to get heavy handed as this point: >>> > >>> > tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) >>> > yum remove ruby puppet facter (remove all your RPMs) >>> > find /usr/lib/ruby (what''s left in your Ruby libdir?) >>> > locate puppet (again, what''s left over, should be almost nothing >>> > but / >>> > var/lib/puppet, /var/run stuff and config files) >>> > >>> > Now you could try reinstall and compare your backed up version of >>> > /usr/ >>> > lib/ruby with your new one. >>> > >>> > On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> >>> > wrote: >>> > >>> >> [root@hproxy11 ~]# locate puppet >>> > ... >>> >> /usr/share/doc/puppet-0.25.5 >>> >>> So... this doesn''t make sense. >>> >>> I just did this on the client: >>> >>> rpm --erase puppet >>> rpm --erase facter >>> find / -name "*facter*" -exec rm -rf {} \; >>> find / -name "*puppet*" -exec rm -rf {} \; >>> >>> And then reinstalled puppet and facter, cleaned the certs etc, and >>> restarted puppet. >>> >>> Problem persists... >> >> maybe these rogue files didnt come from rpm? then it wouldnt know to remove >> them. > > Maybe not, but I''m sure the rm -fR would have taken care of any that > weren''t, no? > > I think we all know that installing puppet 2.7.3 from RPM''s isn''t an > issue, or else everyone would be experiencing the same problem. It > seems at this point, the problem may lie somewhere on the server, > especially as facter locally reports the right value. > > Doug. > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- "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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
If that were true the job of QA would be much easier On Sep 13, 2011 10:48 AM, "Douglas Garstang" <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar <rip@devco.net> wrote: >> >> >> ----- Original Message ----- >>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> >>> wrote: >>> > Err, what is that 0.25-5 doc folder and what RPM owns it? >>> > >>> > rpm -qf /usr/share/doc/puppet-0.25.5 >>> > >>> > If nothing owns it, you''ve pretty much proved your system has old >>> > Puppet artefacts lying around. Personally I wouldn''t trust any of >>> > the >>> > content in /usr/lib/ruby now. Is this a production system? Anything >>> > else use Ruby on it? >>> > >>> > I''d start to get heavy handed as this point: >>> > >>> > tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) >>> > yum remove ruby puppet facter (remove all your RPMs) >>> > find /usr/lib/ruby (what''s left in your Ruby libdir?) >>> > locate puppet (again, what''s left over, should be almost nothing >>> > but / >>> > var/lib/puppet, /var/run stuff and config files) >>> > >>> > Now you could try reinstall and compare your backed up version of >>> > /usr/ >>> > lib/ruby with your new one. >>> > >>> > On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> >>> > wrote: >>> > >>> >> [root@hproxy11 ~]# locate puppet >>> > ... >>> >> /usr/share/doc/puppet-0.25.5 >>> >>> So... this doesn''t make sense. >>> >>> I just did this on the client: >>> >>> rpm --erase puppet >>> rpm --erase facter >>> find / -name "*facter*" -exec rm -rf {} \; >>> find / -name "*puppet*" -exec rm -rf {} \; >>> >>> And then reinstalled puppet and facter, cleaned the certs etc, and >>> restarted puppet. >>> >>> Problem persists... >> >> maybe these rogue files didnt come from rpm? then it wouldnt know toremove>> them. > > Maybe not, but I''m sure the rm -fR would have taken care of any that > weren''t, no? > > I think we all know that installing puppet 2.7.3 from RPM''s isn''t an > issue, or else everyone would be experiencing the same problem. It > seems at this point, the problem may lie somewhere on the server, > especially as facter locally reports the right value. > > Doug. > > -- > 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 topuppet-users+unsubscribe@googlegroups.com.> For more options, visit this group athttp://groups.google.com/group/puppet-users?hl=en.>-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sep 13, 2011, at 10:48 AM, Douglas Garstang wrote:> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar <rip@devco.net> wrote: >> >> >> ----- Original Message ----- >>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> >>> wrote: >>>> Err, what is that 0.25-5 doc folder and what RPM owns it? >>>> >>>> rpm -qf /usr/share/doc/puppet-0.25.5 >>>> >>>> If nothing owns it, you''ve pretty much proved your system has old >>>> Puppet artefacts lying around. Personally I wouldn''t trust any of >>>> the >>>> content in /usr/lib/ruby now. Is this a production system? Anything >>>> else use Ruby on it? >>>> >>>> I''d start to get heavy handed as this point: >>>> >>>> tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) >>>> yum remove ruby puppet facter (remove all your RPMs) >>>> find /usr/lib/ruby (what''s left in your Ruby libdir?) >>>> locate puppet (again, what''s left over, should be almost nothing >>>> but / >>>> var/lib/puppet, /var/run stuff and config files) >>>> >>>> Now you could try reinstall and compare your backed up version of >>>> /usr/ >>>> lib/ruby with your new one. >>>> >>>> On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> >>>> wrote: >>>> >>>>> [root@hproxy11 ~]# locate puppet >>>> ... >>>>> /usr/share/doc/puppet-0.25.5 >>> >>> So... this doesn''t make sense. >>> >>> I just did this on the client: >>> >>> rpm --erase puppet >>> rpm --erase facter >>> find / -name "*facter*" -exec rm -rf {} \; >>> find / -name "*puppet*" -exec rm -rf {} \; >>> >>> And then reinstalled puppet and facter, cleaned the certs etc, and >>> restarted puppet. >>> >>> Problem persists... >> >> maybe these rogue files didnt come from rpm? then it wouldnt know to remove >> them. > > Maybe not, but I''m sure the rm -fR would have taken care of any that > weren''t, no? > > I think we all know that installing puppet 2.7.3 from RPM''s isn''t an > issue, or else everyone would be experiencing the same problem. It > seems at this point, the problem may lie somewhere on the server, > especially as facter locally reports the right value.---- I''m thinking that he has puppet 0.25.5 gem installed and all of the rpm -e / yum remove isn''t going to solve that. try ''gem list --local'' Craig -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 19:28 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 12:25 PM, Craig White <craig.white@ttiltd.com> wrote:> > On Sep 13, 2011, at 10:48 AM, Douglas Garstang wrote: > >> On Tue, Sep 13, 2011 at 10:46 AM, R.I.Pienaar <rip@devco.net> wrote: >>> >>> >>> ----- Original Message ----- >>>> On Tue, Sep 13, 2011 at 1:45 AM, Luke Bigum <Luke.Bigum@lmax.com> >>>> wrote: >>>>> Err, what is that 0.25-5 doc folder and what RPM owns it? >>>>> >>>>> rpm -qf /usr/share/doc/puppet-0.25.5 >>>>> >>>>> If nothing owns it, you''ve pretty much proved your system has old >>>>> Puppet artefacts lying around. Personally I wouldn''t trust any of >>>>> the >>>>> content in /usr/lib/ruby now. Is this a production system? Anything >>>>> else use Ruby on it? >>>>> >>>>> I''d start to get heavy handed as this point: >>>>> >>>>> tar -cvzf /tmp/usrlibruby.tar.gz /usr/lib/ruby (take a backup) >>>>> yum remove ruby puppet facter (remove all your RPMs) >>>>> find /usr/lib/ruby (what''s left in your Ruby libdir?) >>>>> locate puppet (again, what''s left over, should be almost nothing >>>>> but / >>>>> var/lib/puppet, /var/run stuff and config files) >>>>> >>>>> Now you could try reinstall and compare your backed up version of >>>>> /usr/ >>>>> lib/ruby with your new one. >>>>> >>>>> On Sep 12, 11:47 pm, Douglas Garstang <doug.garst...@gmail.com> >>>>> wrote: >>>>> >>>>>> [root@hproxy11 ~]# locate puppet >>>>> ... >>>>>> /usr/share/doc/puppet-0.25.5 >>>> >>>> So... this doesn''t make sense. >>>> >>>> I just did this on the client: >>>> >>>> rpm --erase puppet >>>> rpm --erase facter >>>> find / -name "*facter*" -exec rm -rf {} \; >>>> find / -name "*puppet*" -exec rm -rf {} \; >>>> >>>> And then reinstalled puppet and facter, cleaned the certs etc, and >>>> restarted puppet. >>>> >>>> Problem persists... >>> >>> maybe these rogue files didnt come from rpm? then it wouldnt know to remove >>> them. >> >> Maybe not, but I''m sure the rm -fR would have taken care of any that >> weren''t, no? >> >> I think we all know that installing puppet 2.7.3 from RPM''s isn''t an >> issue, or else everyone would be experiencing the same problem. It >> seems at this point, the problem may lie somewhere on the server, >> especially as facter locally reports the right value. > ---- > I''m thinking that he has puppet 0.25.5 gem installed and all of the rpm -e / yum remove isn''t going to solve that. > > try ''gem list --local''Craig, I posted this yesterday I think, but, on the client: [root@hproxy11 ~]# gem list --local *** LOCAL GEMS *** stomp (1.1.6) Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 19:30 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber <ken@puppetlabs.com> wrote:> Yeah this doesn''t seem to be old versions of Puppet. > > So from my other email ... can you show us the code where you are > doing your comparison for $puppetversion? I have a feeling I might > know what it is ... although I''m probably wrong ... > > In fact - grep for ''puppetversion'' in all of your puppet code ... I''m > curious :-).Ken, The manifest has this: notify{"${puppetversion} on ${fqdn}":} which is causing the following to appear on the server: Sep 13 10:36:51 sv2admin1 puppet-master[22554]: (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on hproxy11.h.foo.com]/message) defined ''message'' as ''0.25.5 on hproxy11.h.foo.com'' and the following to appear on the client: Sep 13 10:36:44 hproxy11 puppet-agent[12366]: (/Stage[main]/Puppet::Setup/Notify[0.25.5 on hproxy11.h.foocom]/message) defined ''message'' as ''0.25.5 on hproxy11.h.foo.com'' Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
So that is the only case where you are using the variable throughout your entire code? I mean - ALL your code ... not just the one line you are printing to the screen ... ken. On Tue, Sep 13, 2011 at 8:30 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber <ken@puppetlabs.com> wrote: >> Yeah this doesn''t seem to be old versions of Puppet. >> >> So from my other email ... can you show us the code where you are >> doing your comparison for $puppetversion? I have a feeling I might >> know what it is ... although I''m probably wrong ... >> >> In fact - grep for ''puppetversion'' in all of your puppet code ... I''m >> curious :-). > > Ken, > > The manifest has this: > > notify{"${puppetversion} on ${fqdn}":} > > which is causing the following to appear on the server: > > Sep 13 10:36:51 sv2admin1 puppet-master[22554]: > (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on > hproxy11.h.foo.com]/message) defined ''message'' as ''0.25.5 on > hproxy11.h.foo.com'' > > and the following to appear on the client: > > Sep 13 10:36:44 hproxy11 puppet-agent[12366]: > (/Stage[main]/Puppet::Setup/Notify[0.25.5 on > hproxy11.h.foocom]/message) defined ''message'' as ''0.25.5 on > hproxy11.h.foo.com'' > > Doug > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- "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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Sep 13, 2011, at 12:28 PM, Douglas Garstang wrote:> On Tue, Sep 13, 2011 at 12:25 PM, Craig White <craig.white@ttiltd.com> wrote: >> >> I''m thinking that he has puppet 0.25.5 gem installed and all of the rpm -e / yum remove isn''t going to solve that. >> >> try ''gem list --local'' > > Craig, I posted this yesterday I think, but, on the client: > > [root@hproxy11 ~]# gem list --local > > *** LOCAL GEMS *** > > stomp (1.1.6)---- it is possible to have more than 1 ruby installed and more than 1 gem local store and then users can store gems in their home directories too. There''s an amazing amount of ways to shoot yourself in the foot with local installations of ruby. Our company gave up on the rpm/apt packages and simply uses enterprise-ruby and gems to install everything. I have removed all distribution packages of anything remotely resembling ruby and life is much simpler. Got snagged when I first started playing with puppet because I was also playing with chef and used Ubuntu''s packages for ruby/gems/etc. and that clearly wasn''t working well. Craig -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
The reason why I say this - is because I can replicate this problem myself with:
node default {
$puppetversion = "0.25.5"
notice($puppetversion)
}
In fact its the only way I can think of to replicate the issue -
besides all the other ways we have already ruled out. *shrug*.
ken.
On Tue, Sep 13, 2011 at 8:34 PM, Ken Barber <ken@puppetlabs.com>
wrote:> So that is the only case where you are using the variable throughout
> your entire code? I mean - ALL your code ... not just the one line you
> are printing to the screen ...
>
> ken.
>
> On Tue, Sep 13, 2011 at 8:30 PM, Douglas Garstang
> <doug.garstang@gmail.com> wrote:
>> On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber <ken@puppetlabs.com>
wrote:
>>> Yeah this doesn''t seem to be old versions of Puppet.
>>>
>>> So from my other email ... can you show us the code where you are
>>> doing your comparison for $puppetversion? I have a feeling I might
>>> know what it is ... although I''m probably wrong ...
>>>
>>> In fact - grep for ''puppetversion'' in all of your
puppet code ... I''m
>>> curious :-).
>>
>> Ken,
>>
>> The manifest has this:
>>
>> notify{"${puppetversion} on ${fqdn}":}
>>
>> which is causing the following to appear on the server:
>>
>> Sep 13 10:36:51 sv2admin1 puppet-master[22554]:
>> (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on
>> hproxy11.h.foo.com]/message) defined ''message'' as
''0.25.5 on
>> hproxy11.h.foo.com''
>>
>> and the following to appear on the client:
>>
>> Sep 13 10:36:44 hproxy11 puppet-agent[12366]:
>> (/Stage[main]/Puppet::Setup/Notify[0.25.5 on
>> hproxy11.h.foocom]/message) defined ''message'' as
''0.25.5 on
>> hproxy11.h.foo.com''
>>
>> Doug
>>
>> --
>> 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+unsubscribe@googlegroups.com.
>> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>>
>>
>
>
>
> --
> "Join us for PuppetConf, September 22nd and 23rd in Portland, OR:
> http://bit.ly/puppetconfsig"
>
--
"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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Even using:
notify{"${::puppetversion} on ${::fqdn}":}
Instead would be of interest ...
ken.
On Tue, Sep 13, 2011 at 8:46 PM, Ken Barber <ken@puppetlabs.com>
wrote:> The reason why I say this - is because I can replicate this problem myself
with:
>
> node default {
> $puppetversion = "0.25.5"
> notice($puppetversion)
> }
>
> In fact its the only way I can think of to replicate the issue -
> besides all the other ways we have already ruled out. *shrug*.
>
> ken.
>
> On Tue, Sep 13, 2011 at 8:34 PM, Ken Barber <ken@puppetlabs.com>
wrote:
>> So that is the only case where you are using the variable throughout
>> your entire code? I mean - ALL your code ... not just the one line you
>> are printing to the screen ...
>>
>> ken.
>>
>> On Tue, Sep 13, 2011 at 8:30 PM, Douglas Garstang
>> <doug.garstang@gmail.com> wrote:
>>> On Tue, Sep 13, 2011 at 11:01 AM, Ken Barber
<ken@puppetlabs.com> wrote:
>>>> Yeah this doesn''t seem to be old versions of Puppet.
>>>>
>>>> So from my other email ... can you show us the code where you
are
>>>> doing your comparison for $puppetversion? I have a feeling I
might
>>>> know what it is ... although I''m probably wrong ...
>>>>
>>>> In fact - grep for ''puppetversion'' in all of
your puppet code ... I''m
>>>> curious :-).
>>>
>>> Ken,
>>>
>>> The manifest has this:
>>>
>>> notify{"${puppetversion} on ${fqdn}":}
>>>
>>> which is causing the following to appear on the server:
>>>
>>> Sep 13 10:36:51 sv2admin1 puppet-master[22554]:
>>> (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on
>>> hproxy11.h.foo.com]/message) defined ''message'' as
''0.25.5 on
>>> hproxy11.h.foo.com''
>>>
>>> and the following to appear on the client:
>>>
>>> Sep 13 10:36:44 hproxy11 puppet-agent[12366]:
>>> (/Stage[main]/Puppet::Setup/Notify[0.25.5 on
>>> hproxy11.h.foocom]/message) defined ''message'' as
''0.25.5 on
>>> hproxy11.h.foo.com''
>>>
>>> Doug
>>>
>>> --
>>> 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+unsubscribe@googlegroups.com.
>>> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>>>
>>>
>>
>>
>>
>> --
>> "Join us for PuppetConf, September 22nd and 23rd in Portland, OR:
>> http://bit.ly/puppetconfsig"
>>
>
>
>
> --
> "Join us for PuppetConf, September 22nd and 23rd in Portland, OR:
> http://bit.ly/puppetconfsig"
>
--
"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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 20:01 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 12:46 PM, Ken Barber <ken@puppetlabs.com> wrote:> The reason why I say this - is because I can replicate this problem myself with: > > node default { > $puppetversion = "0.25.5" > notice($puppetversion) > } > > In fact its the only way I can think of to replicate the issue - > besides all the other ways we have already ruled out. *shrug*.Ken, I thought about that earlier, and checked. This is on the puppet master: [root@sv2admin1 puppet]# find /etc/puppet | xargs grep puppetversion | grep -v ".svn" /etc/puppet/modules/puppet/manifests/init.pp: #notice ("fqdn ${fqdn}, puppetversion = ${puppetversion}") /etc/puppet/modules/puppet/manifests/init.pp: notify{"${puppetversion} on ${fqdn}":} /etc/puppet/modules/puppet/manifests/init.pp: source => $puppetversion ? { Only references are the ones I am aware of. The puppetversion variable isn''t being assigned anywhere that I can see. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Hmm ... well can you try using ${::puppetversion} ...?
Also - I notice you are using an ENC ... can you disable that and just
use node entries? Yet another place where we might be getting vars we
don''t expect. In fact - setup a site.pp that is really blank - and
only contains that notify statement ...
ken.
On Tue, Sep 13, 2011 at 9:01 PM, Douglas Garstang
<doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 12:46 PM, Ken Barber <ken@puppetlabs.com>
wrote:
>> The reason why I say this - is because I can replicate this problem
myself with:
>>
>> node default {
>> $puppetversion = "0.25.5"
>> notice($puppetversion)
>> }
>>
>> In fact its the only way I can think of to replicate the issue -
>> besides all the other ways we have already ruled out. *shrug*.
>
> Ken, I thought about that earlier, and checked.
>
> This is on the puppet master:
> [root@sv2admin1 puppet]# find /etc/puppet | xargs grep puppetversion |
> grep -v ".svn"
> /etc/puppet/modules/puppet/manifests/init.pp: #notice ("fqdn
> ${fqdn}, puppetversion = ${puppetversion}")
> /etc/puppet/modules/puppet/manifests/init.pp:
> notify{"${puppetversion} on ${fqdn}":}
> /etc/puppet/modules/puppet/manifests/init.pp: source
> => $puppetversion ? {
>
> Only references are the ones I am aware of. The puppetversion variable
> isn''t being assigned anywhere that I can see.
>
> Doug.
>
> --
> 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+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
>
>
--
"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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 22:21 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber <ken@puppetlabs.com> wrote:> Hmm ... well can you try using ${::puppetversion} ...?Adding this: notify{"xxx = ${::puppetversion} ...":} to the manifest gives this on the server: Sep 13 15:14:43 sv2admin1 puppet-master[22452]: (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on hproxy11.h.foo.com]/message) defined ''message'' as ''0.25.5 on hproxy11.h.foo.com'' and this on the client: Sep 13 15:14:13 hproxy11 puppet-agent[20393]: (/Stage[main]/Puppet::Setup/Notify[xxx = 0.25.5 ...]/message) defined ''message'' as ''xxx = 0.25.5 ...'' We''re not using an ENC for this node, but the node definition for this node is: node /^hproxy[0-9]+/ { $hosttype = "proxy" $ganglia_cluster_name = "hproxy" $ganglia_cluster_hosts = ["hproxy00", "hproxy01", "hproxy10",] include ganglia::gmond::setup include monitoring::lb_status include zone::hcluster include app::base::setup include app::proxy::setup }> > Also - I notice you are using an ENC ... can you disable that and just > use node entries? Yet another place where we might be getting vars we > don''t expect. In fact - setup a site.pp that is really blank - and > only contains that notify statement ...So, I went and put this and ONLY this in /etc/puppet/manifests/site.pp: notify{"yyy = ${::puppetversion} ...":} and got this on the server: Sep 13 15:18:08 sv2admin1 puppet-master[22503]: (//hproxy11.h.foo.com/Puppet) xxx = 0.25.5 ... and this on the client: Sep 13 15:18:27 hproxy11 puppet-agent[23962]: (/Stage[main]//Notify[yyy = 0.25.5 ...]/message) defined ''message'' as ''yyy = 0.25.5 ...'' So.... it really seems like something is seriously screwed up here.... with the server. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 23:01 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber <ken@puppetlabs.com> wrote: >> Hmm ... well can you try using ${::puppetversion} ...? > > Adding this: > > notify{"xxx = ${::puppetversion} ...":} > > to the manifest gives this on the server: > > Sep 13 15:14:43 sv2admin1 puppet-master[22452]: > (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on > hproxy11.h.foo.com]/message) defined ''message'' as ''0.25.5 on > hproxy11.h.foo.com'' > > and this on the client: > > Sep 13 15:14:13 hproxy11 puppet-agent[20393]: > (/Stage[main]/Puppet::Setup/Notify[xxx = 0.25.5 ...]/message) defined > ''message'' as ''xxx = 0.25.5 ...'' > > We''re not using an ENC for this node, but the node definition for this node is: > > node /^hproxy[0-9]+/ { > $hosttype = "proxy" > $ganglia_cluster_name = "hproxy" > $ganglia_cluster_hosts = ["hproxy00", "hproxy01", "hproxy10",] > include ganglia::gmond::setup > include monitoring::lb_status > include zone::hcluster > include app::base::setup > include app::proxy::setup > } > >> >> Also - I notice you are using an ENC ... can you disable that and just >> use node entries? Yet another place where we might be getting vars we >> don''t expect. In fact - setup a site.pp that is really blank - and >> only contains that notify statement ... > > So, I went and put this and ONLY this in /etc/puppet/manifests/site.pp: > > notify{"yyy = ${::puppetversion} ...":} > > and got this on the server: > > Sep 13 15:18:08 sv2admin1 puppet-master[22503]: > (//hproxy11.h.foo.com/Puppet) xxx = 0.25.5 ... > > and this on the client: > > Sep 13 15:18:27 hproxy11 puppet-agent[23962]: > (/Stage[main]//Notify[yyy = 0.25.5 ...]/message) defined ''message'' as > ''yyy = 0.25.5 ...'' > > So.... it really seems like something is seriously screwed up here.... > with the server. > > Doug. >I also just ran this on the server: [root@sv2admin1 ~]# find / -name "*puppet*" -exec grep PUPPETVERSION {} \; PUPPETVERSION = ''2.7.3'' PUPPETVERSION Puppet::PUPPETVERSION.to_s PUPPETVERSION = ''2.7.3'' PUPPETVERSION Puppet::PUPPETVERSION.to_s PUPPETVERSION = ''2.6.3'' PUPPETVERSION [root@sv2admin1 ~]# Strange that it finds 2.6.3, but not 0.25.5... Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 23:16 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang > <doug.garstang@gmail.com> wrote: >> On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber <ken@puppetlabs.com> wrote: >>> Hmm ... well can you try using ${::puppetversion} ...? >> >> Adding this: >> >> notify{"xxx = ${::puppetversion} ...":} >> >> to the manifest gives this on the server: >> >> Sep 13 15:14:43 sv2admin1 puppet-master[22452]: >> (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on >> hproxy11.h.foo.com]/message) defined ''message'' as ''0.25.5 on >> hproxy11.h.foo.com'' >> >> and this on the client: >> >> Sep 13 15:14:13 hproxy11 puppet-agent[20393]: >> (/Stage[main]/Puppet::Setup/Notify[xxx = 0.25.5 ...]/message) defined >> ''message'' as ''xxx = 0.25.5 ...'' >> >> We''re not using an ENC for this node, but the node definition for this node is: >> >> node /^hproxy[0-9]+/ { >> $hosttype = "proxy" >> $ganglia_cluster_name = "hproxy" >> $ganglia_cluster_hosts = ["hproxy00", "hproxy01", "hproxy10",] >> include ganglia::gmond::setup >> include monitoring::lb_status >> include zone::hcluster >> include app::base::setup >> include app::proxy::setup >> } >> >>> >>> Also - I notice you are using an ENC ... can you disable that and just >>> use node entries? Yet another place where we might be getting vars we >>> don''t expect. In fact - setup a site.pp that is really blank - and >>> only contains that notify statement ... >> >> So, I went and put this and ONLY this in /etc/puppet/manifests/site.pp: >> >> notify{"yyy = ${::puppetversion} ...":} >> >> and got this on the server: >> >> Sep 13 15:18:08 sv2admin1 puppet-master[22503]: >> (//hproxy11.h.foo.com/Puppet) xxx = 0.25.5 ... >> >> and this on the client: >> >> Sep 13 15:18:27 hproxy11 puppet-agent[23962]: >> (/Stage[main]//Notify[yyy = 0.25.5 ...]/message) defined ''message'' as >> ''yyy = 0.25.5 ...'' >> >> So.... it really seems like something is seriously screwed up here.... >> with the server. >> >> Doug. >> > > I also just ran this on the server: > > > [root@sv2admin1 ~]# find / -name "*puppet*" -exec grep PUPPETVERSION {} \; > PUPPETVERSION = ''2.7.3'' > PUPPETVERSION > Puppet::PUPPETVERSION.to_s > PUPPETVERSION = ''2.7.3'' > PUPPETVERSION > Puppet::PUPPETVERSION.to_s > PUPPETVERSION = ''2.6.3'' > PUPPETVERSION > [root@sv2admin1 ~]# > > Strange that it finds 2.6.3, but not 0.25.5... > > Doug. >I also just ran puppet on a fresh client, one that never had the 0.25.5 version of puppet installed. I get this: Sep 13 16:14:47 hproxy11 puppet-agent[13430]: xxx = 0.25.5 ... Sep 13 16:14:47 hproxy11 puppet-agent[13430]: (/Stage[main]/Puppet::Setup/Notify[xxx = 0.25.5 ...]/message) defined ''message'' as ''xxx = 0.25.5 ...'' Sep 13 16:14:57 hproxy11 puppet-agent[13430]: 0.25.5 on hproxy11.h.fo.com So, obviously this is a server side issue. Where can I look on the server? Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
You could always do one of your crazy greps :-). Out of curiosity - what do your /var/lib/puppet/yaml/facts/*.yaml files show you on your server? ken. On Wed, Sep 14, 2011 at 12:16 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang > <doug.garstang@gmail.com> wrote: >> On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >>> On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber <ken@puppetlabs.com> wrote: >>>> Hmm ... well can you try using ${::puppetversion} ...? >>> >>> Adding this: >>> >>> notify{"xxx = ${::puppetversion} ...":} >>> >>> to the manifest gives this on the server: >>> >>> Sep 13 15:14:43 sv2admin1 puppet-master[22452]: >>> (//hproxy11.h.foo.com//Stage[main]/Puppet::Setup/Notify[0.25.5 on >>> hproxy11.h.foo.com]/message) defined ''message'' as ''0.25.5 on >>> hproxy11.h.foo.com'' >>> >>> and this on the client: >>> >>> Sep 13 15:14:13 hproxy11 puppet-agent[20393]: >>> (/Stage[main]/Puppet::Setup/Notify[xxx = 0.25.5 ...]/message) defined >>> ''message'' as ''xxx = 0.25.5 ...'' >>> >>> We''re not using an ENC for this node, but the node definition for this node is: >>> >>> node /^hproxy[0-9]+/ { >>> $hosttype = "proxy" >>> $ganglia_cluster_name = "hproxy" >>> $ganglia_cluster_hosts = ["hproxy00", "hproxy01", "hproxy10",] >>> include ganglia::gmond::setup >>> include monitoring::lb_status >>> include zone::hcluster >>> include app::base::setup >>> include app::proxy::setup >>> } >>> >>>> >>>> Also - I notice you are using an ENC ... can you disable that and just >>>> use node entries? Yet another place where we might be getting vars we >>>> don''t expect. In fact - setup a site.pp that is really blank - and >>>> only contains that notify statement ... >>> >>> So, I went and put this and ONLY this in /etc/puppet/manifests/site.pp: >>> >>> notify{"yyy = ${::puppetversion} ...":} >>> >>> and got this on the server: >>> >>> Sep 13 15:18:08 sv2admin1 puppet-master[22503]: >>> (//hproxy11.h.foo.com/Puppet) xxx = 0.25.5 ... >>> >>> and this on the client: >>> >>> Sep 13 15:18:27 hproxy11 puppet-agent[23962]: >>> (/Stage[main]//Notify[yyy = 0.25.5 ...]/message) defined ''message'' as >>> ''yyy = 0.25.5 ...'' >>> >>> So.... it really seems like something is seriously screwed up here.... >>> with the server. >>> >>> Doug. >>> >> >> I also just ran this on the server: >> >> >> [root@sv2admin1 ~]# find / -name "*puppet*" -exec grep PUPPETVERSION {} \; >> PUPPETVERSION = ''2.7.3'' >> PUPPETVERSION >> Puppet::PUPPETVERSION.to_s >> PUPPETVERSION = ''2.7.3'' >> PUPPETVERSION >> Puppet::PUPPETVERSION.to_s >> PUPPETVERSION = ''2.6.3'' >> PUPPETVERSION >> [root@sv2admin1 ~]# >> >> Strange that it finds 2.6.3, but not 0.25.5... >> >> Doug. >> > > I also just ran puppet on a fresh client, one that never had the > 0.25.5 version of puppet installed. I get this: > > Sep 13 16:14:47 hproxy11 puppet-agent[13430]: xxx = 0.25.5 ... > Sep 13 16:14:47 hproxy11 puppet-agent[13430]: > (/Stage[main]/Puppet::Setup/Notify[xxx = 0.25.5 ...]/message) defined > ''message'' as ''xxx = 0.25.5 ...'' > Sep 13 16:14:57 hproxy11 puppet-agent[13430]: 0.25.5 on hproxy11.h.fo.com > > So, obviously this is a server side issue. Where can I look on the server? > > Doug > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- "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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 23:33 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 4:27 PM, Ken Barber <ken@puppetlabs.com> wrote:> You could always do one of your crazy greps :-).:(> > Out of curiosity - what do your /var/lib/puppet/yaml/facts/*.yaml > files show you on your server?clientversion: &id001 0.25.5 :( Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
How are you running your puppet master? Can you try it with just: puppet master --debug --no-daemonize Just there was a thread I recall about Mongrel - it may not be related: http://groups.google.com/group/puppet-users/browse_thread/thread/3f4072d375851ee7 It would be nice to see a packet capture from the client of facts to rule out the client ... but I''m not 100% on the technique as its SSL. I''ll do some research - but maybe someone else can chime in. ken. On Wed, Sep 14, 2011 at 12:33 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Tue, Sep 13, 2011 at 4:27 PM, Ken Barber <ken@puppetlabs.com> wrote: >> You could always do one of your crazy greps :-). > > :( > >> >> Out of curiosity - what do your /var/lib/puppet/yaml/facts/*.yaml >> files show you on your server? > > clientversion: &id001 0.25.5 > > :( > > Doug > > -- > 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+unsubscribe@googlegroups.com. > For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en. > >-- "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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-13 23:53 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 4:43 PM, Ken Barber <ken@puppetlabs.com> wrote:> How are you running your puppet master? > > Can you try it with just: > > puppet master --debug --no-daemonize > > Just there was a thread I recall about Mongrel - it may not be related: > > http://groups.google.com/group/puppet-users/browse_thread/thread/3f4072d375851ee7I think this may be totally related. We''re using mongrel... AND, running the puppet master in standalone mode as you suggested yields this now on the client: Sep 13 16:49:06 hproxy11 puppet-agent[27311]: (/Stage[main]/Puppet::Setup/Notify[xxx = 2.7.3 ...]/message) defined ''message'' as ''xxx = 2.7.3 ...'' I couldn''t find the corresponding message on the server. Looks like a similar issue to what is happening in that other thread.... except in their case the values are empty, and in my case they are plain wrong. :( One step closer at least. Doug. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> I think this may be totally related. We''re using mongrel... AND, > running the puppet master in standalone mode as you suggested yields > this now on the client: > > Sep 13 16:49:06 hproxy11 puppet-agent[27311]: > (/Stage[main]/Puppet::Setup/Notify[xxx = 2.7.3 ...]/message) defined > ''message'' as ''xxx = 2.7.3 ...'' > > I couldn''t find the corresponding message on the server. > > Looks like a similar issue to what is happening in that other > thread.... except in their case the values are empty, and in my case > they are plain wrong. :( > > One step closer at least.Well yes - the first sign of success we''ve had all week :-). I can probably get some sleep now. (its like 1 am in London). The sad thing is - I half-suggested this much earlier in the thread but thought it might be overkill for the problem. To me - it seems like data is getting mismatched across sessions perhaps? I''m guessing you have 0.25.5 clients checking into your server for example. I know absolutely nothing about Mongrel and Puppet myself having always used Passenger. Do you have clear instructions on how you set this up for yourself somewhere that you can provide us all? Include revisions, config and rpms you may have downloaded from where-ever? We would want to be able to reproduce this to fix it ... so anything you can do to help would be great. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Douglas Garstang
2011-Sep-14 00:16 UTC
Re: [Puppet Users] Re: Facter variable $puppetversion
On Tue, Sep 13, 2011 at 5:12 PM, Ken Barber <ken@puppetlabs.com> wrote:>> I think this may be totally related. We''re using mongrel... AND, >> running the puppet master in standalone mode as you suggested yields >> this now on the client: >> >> Sep 13 16:49:06 hproxy11 puppet-agent[27311]: >> (/Stage[main]/Puppet::Setup/Notify[xxx = 2.7.3 ...]/message) defined >> ''message'' as ''xxx = 2.7.3 ...'' >> >> I couldn''t find the corresponding message on the server. >> >> Looks like a similar issue to what is happening in that other >> thread.... except in their case the values are empty, and in my case >> they are plain wrong. :( >> >> One step closer at least. > > Well yes - the first sign of success we''ve had all week :-). I can > probably get some sleep now. (its like 1 am in London). The sad thing > is - I half-suggested this much earlier in the thread but thought it > might be overkill for the problem. > > To me - it seems like data is getting mismatched across sessions > perhaps? I''m guessing you have 0.25.5 clients checking into your > server for example. > > I know absolutely nothing about Mongrel and Puppet myself having > always used Passenger. Do you have clear instructions on how you set > this up for yourself somewhere that you can provide us all? Include > revisions, config and rpms you may have downloaded from where-ever? > > We would want to be able to reproduce this to fix it ... so anything > you can do to help would be great.Ken, Thanks for your help. Unfortunately, I can''t tell you much about the setup. I''ve only ever done this with passenger as well, and the person who did set it up has left the company. I wonder if the performance of the puppet master in 2.7.3 has increased to the point where passenger/mongrel aren''t really required anymore? I''m running puppet in standalone debug right now, and forced 40 or so clients to reconnect, and the load avg on the server never went above about 1. Maybe we can throw mongrel away. We have about 500 servers. Doug -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
On Tue, Sep 13, 2011 at 5:16 PM, Douglas Garstang <doug.garstang@gmail.com>wrote:> > I wonder if the performance of the puppet master in 2.7.3 has > increased to the point where passenger/mongrel aren''t really required > anymore? I''m running puppet in standalone debug right now, and forced > 40 or so clients to reconnect, and the load avg on the server never > went above about 1. Maybe we can throw mongrel away. We have about 500 > servers. > >I wouldn''t run 500 servers on the webrick server, particularly not with any degree of concurrency, but maybe I''m being too pessimistic here. Migrating from mongrel to passenger really is a relatively quick task that you can develop in parallel on a different port. -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
> Thanks for your help. Unfortunately, I can''t tell you much about the > setup. I''ve only ever done this with passenger as well, and the person > who did set it up has > left the company.I''m not really sure if you should raise a new ticket on this one - or add an addendum to this: http://projects.puppetlabs.com/issues/9109 These issues do seem somewhat related, but the symptoms are slightly different. Either way - if you can log something within Redmine with all the details you have and a link to this thread that would be much appreciated Doug. 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
jsellens@syonex.com
2011-Oct-12 19:48 UTC
[Puppet Users] Re: Facter variable $puppetversion
Following on to http://groups.google.com/group/puppet-users/browse_thread/thread/271f6f6522524207/c90596d1823a1bbf As another data point - I was seeing the same wrong values for $puppetversion on the puppet master - the client says one thing, the server says another. This is puppet 2.7.5. Now I''m seeing something similar which I suspect is related. I have a FreeBSD puppet client, but the cached yaml/node/hostname.yaml file on the puppet master has variables with values from the puppet master, not the client - notably kernel, operatingsystem, operatingsystemrelease, and others. Some are correct, like processor0, macaddress, manufacturer, fwdn, hostname, swapfree, ... There''s a mix of values from the server and from the client. I''m also seeing the problem with one client where it knows all its facts, but the server has none. Happy to provide more details if it would be useful. Thanks! John -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.