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.garst...@gmail.com> wrote:
> On Tue, Sep 13, 2011 at 4:01 PM, Douglas Garstang
> <doug.garst...@gmail.com> wrote:
>> On Tue, Sep 13, 2011 at 3:21 PM, Douglas Garstang
>> <doug.garst...@gmail.com> wrote:
>>> On Tue, Sep 13, 2011 at 1:06 PM, Ken Barber <k...@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+unsubscr...@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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
