I''m seeing very similar problem to what''s described in http://reductivelabs.com/trac/puppet/ticket/1147 debug: importing ''/opt/puppet/manifests/nodes.pp'' notice: Scope(Node[default]): lsbdistcodename is . notice: Scope(Node[default]): lsbdistid is . notice: Scope(Node[default]): ipaddress is . notice: Scope(Node[default]): fqdn is . notice: Scope(Node[default]): operatingsystem is . debug: No true answers and no default How can I purge out the cached node definition? -- Mark Foster - Sr. Systems Engineer - BitPusher, LLC We push your bits so you don''t have to! http://www.bitpusher.com/ --~--~---------~--~----~------------~-------~--~----~ 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 May 8, 2008, at 3:54 PM, Mark Foster wrote:> > I''m seeing very similar problem to what''s described in > http://reductivelabs.com/trac/puppet/ticket/1147 > > debug: importing ''/opt/puppet/manifests/nodes.pp'' > notice: Scope(Node[default]): lsbdistcodename is . > notice: Scope(Node[default]): lsbdistid is . > notice: Scope(Node[default]): ipaddress is . > notice: Scope(Node[default]): fqdn is . > notice: Scope(Node[default]): operatingsystem is . > debug: No true answers and no default > > How can I purge out the cached node definition?It''s cached in the yamldir on the server, so just remove the node file. -- Love is the triumph of imagination over intelligence. -- H. L. Mencken --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> On May 8, 2008, at 3:54 PM, Mark Foster wrote: > > >> I''m seeing very similar problem to what''s described in >> http://reductivelabs.com/trac/puppet/ticket/1147 >> >> debug: importing ''/opt/puppet/manifests/nodes.pp'' >> notice: Scope(Node[default]): lsbdistcodename is . >> notice: Scope(Node[default]): lsbdistid is . >> notice: Scope(Node[default]): ipaddress is . >> notice: Scope(Node[default]): fqdn is . >> notice: Scope(Node[default]): operatingsystem is . >> debug: No true answers and no default >> >> How can I purge out the cached node definition? >> > > It''s cached in the yamldir on the server, so just remove the node file. > >OK so I''m removing /var/lib/puppet/yaml/node/default.yaml and it keeps being recreated just the same. On debug output from puppetmasterd (when client connects) I see: ... debug: Allowing authenticated client mtl2-50620.nsd.org(10.12.9.12) access to puppetmaster.getconfig debug: Our client is remote info: Using cached node default notice: Using default node for mtl2-50620.nsd.org notice: Scope(Node[default]): lsbdistcodename is . notice: Scope(Node[default]): operatingsystem is . debug: No true answers and no default notice: Compiled configuration for mtl2-50620.nsd.org in 0.01 seconds ... My nodes.pp contains... node default { notice("lsbdistcodename is ${lsbdistcodename}.") notice("operatingsystem is ${operatingsystem}.") #include $operatinsystem case $operatingsystem { Darwin: { include darwin } # apply the darwin class darwin: { include darwin } # apply the darwin class debian: { include debian } # apply the debian class } } Neither the "include $operatingsystem" or the "case $operatingsystem" is doing anything of value. Please help. Thanks. -- Mark Foster - Sr. Systems Engineer - BitPusher, LLC We push your bits so you don''t have to! http://www.bitpusher.com/ --~--~---------~--~----~------------~-------~--~----~ 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 May 16, 2008, at 2:34 PM, Mark Foster wrote:> OK so I''m removing /var/lib/puppet/yaml/node/default.yaml > and it keeps being recreated just the same. > On debug output from puppetmasterd (when client connects) I see: > ... > debug: Allowing authenticated client mtl2-50620.nsd.org(10.12.9.12) > access to puppetmaster.getconfig > debug: Our client is remote > info: Using cached node default > notice: Using default node for mtl2-50620.nsd.org > notice: Scope(Node[default]): lsbdistcodename is . > notice: Scope(Node[default]): operatingsystem is . > debug: No true answers and no default > notice: Compiled configuration for mtl2-50620.nsd.org in 0.01 seconds > [...] > > Neither the "include $operatingsystem" or the "case > $operatingsystem" is > doing anything of value.Is ''node_name'' set to ''facter'' in your system? If that''s the case, then you''re getting hit with #1178, which I will be fixing before the next release. Otherwise, I don''t know what''s causing that. It works for most people, so there must be something somewhat different about your setup. -- Zeilinger''s Fundamental Law: There is no Fundamental Law. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> Is ''node_name'' set to ''facter'' in your system?Not explicitly set, so it defaults to ''cert'' right?.> If that''s the case, then you''re getting hit with #1178, which I will > be fixing before the next release. > > Otherwise, I don''t know what''s causing that. It works for most > people, so there must be something somewhat different about your setup. > >I''m using node_terminus = ldap. When I remove that line from puppet.conf the problem goes away. $operatingsystem is defined and so the include works. So it''s some strangeness where having the default node in LDAP strips the facts. -- Mark Foster - Sr. Systems Engineer - BitPusher, LLC We push your bits so you don''t have to! http://www.bitpusher.com/ --~--~---------~--~----~------------~-------~--~----~ 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 May 16, 2008, at 3:46 PM, Mark Foster wrote:> > Luke Kanies wrote: >> Is ''node_name'' set to ''facter'' in your system? > Not explicitly set, so it defaults to ''cert'' right?. >> If that''s the case, then you''re getting hit with #1178, which I will >> be fixing before the next release. >> >> Otherwise, I don''t know what''s causing that. It works for most >> people, so there must be something somewhat different about your >> setup. >> >> > I''m using node_terminus = ldap. When I remove that line from > puppet.conf > the problem goes away. > $operatingsystem is defined and so the include works. > So it''s some strangeness where having the default node in LDAP strips > the facts.It''s probably safe to assume you''re getting hit with the same bug, then. You''ll probably find that your node cache is named differently than your facts cache. If you don''t have too many hosts, you can hackishly symlink the facts so that the names match. -- Hoare''s Law of Large Problems: Inside every large problem is a small problem struggling to get out. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Just to close the loop on this, I was tripping myself up trying to do includes in a default node defined in a (file-based) nodes.pp while also pointing to LDAP. Since node_terminus=ldap I realized I needed to make it work with the default node *IN LDAP*, so I added puppetclass: basenode and defined a basenode class to do the ''include $operatingsystem'' from. Works fine now, just needed some Elmer''s glue so to speak :). Thanks for the help and sorry for the noise. Deleting nodes.pp 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> On May 8, 2008, at 3:54 PM, Mark Foster wrote: > > >> I''m seeing very similar problem to what''s described in >> http://reductivelabs.com/trac/puppet/ticket/1147 >> >> debug: importing ''/opt/puppet/manifests/nodes.pp'' >> notice: Scope(Node[default]): lsbdistcodename is . >> notice: Scope(Node[default]): lsbdistid is . >> notice: Scope(Node[default]): ipaddress is . >> notice: Scope(Node[default]): fqdn is . >> notice: Scope(Node[default]): operatingsystem is . >> debug: No true answers and no default >> >> How can I purge out the cached node definition? >> > > It''s cached in the yamldir on the server, so just remove the node file. > >I hate to bring this up again but problem of facter vars getting "lost" is back. Please let me know if I should file as a bug? My environment: Servers: 2 debian etch running puppet 0.24.4 (deb) puppetmaster nodes using NFS-backed storage (/opt/puppet) for $ssldir, (manifests and files) are pulled from subversion via post-commit hook, LDAP directory for nodes. Clients: debian etch running 0.24.4 gem, darwin 10.4, 10.5 running 0.24.4 gem 1. default node in ldap belongs to puppetclass: baseclass dn: cn=default,ou=Hosts,dc=nsd,dc=org cn: default objectClass: device objectClass: ipHost objectClass: top objectClass: puppetClient ipHostNumber: 10.0.0.0 description: The default node puppetClass: baseclass 2. baseclass contains class baseclass { notice("Reached class: baseclass") notice("lsbdistcodename is ${lsbdistcodename}.") notice("operatingsystem is ${operatingsystem}.") include $operatingsystem } ...I run puppetd # /var/lib/gems/1.8/bin/puppetd --verbose --no-daemonize warning: peer certificate won''t be verified in this SSL session notice: Got signed certificate notice: Starting Puppet client version 0.24.4 info: Caching catalog at /var/puppet/state/localconfig.yaml notice: Starting catalog run info: Creating state file /var/puppet/state/state.yaml notice: Finished catalog run in 0.02 seconds (e.g. nothing happens, even on a brand new node). ...Puppetmaster output... $ /usr/sbin/puppetmasterd --verbose --debug --no-daemonize ... info: Listening on port 8140 notice: Starting Puppet server version 0.24.4 notice: Allowing unauthenticated client bptest05(10.1.37.25) access to puppetca.getcert info: Signing certificate for bptest05.nsd.org debug: Overriding bptest05 with cert name bptest05.nsd.org debug: Allowing authenticated client bptest05.nsd.org(10.1.37.25) access to puppetmaster.getconfig debug: Our client is remote debug: Creating default schedules debug: Finishing transaction -610946048 with 0 changes debug: Creating default schedules debug: Finishing transaction -608577448 with 0 changes info: Using cached node default notice: Using default node for bptest05.nsd.org debug: importing ''/opt/puppet/manifests/classes/cpan.pp'' debug: importing ''/opt/puppet/manifests/classes/baseclass.pp'' debug: importing ''/opt/puppet/manifests/classes/sshserver.pp'' debug: importing ''/opt/puppet/manifests/classes/breadcrumb.pp'' debug: importing ''/opt/puppet/manifests/classes/testing.pp'' debug: importing ''/opt/puppet/manifests/classes/sudo.pp'' debug: importing ''/opt/puppet/manifests/classes/darwin.pp'' debug: importing ''/opt/puppet/manifests/classes/basenode.pp'' debug: importing ''/opt/puppet/manifests/classes/syslog-client.pp'' debug: importing ''/opt/puppet/manifests/classes/snmpd.pp'' debug: importing ''/opt/puppet/manifests/classes/debian.pp'' notice: Scope(Class[baseclass]): Reached class: baseclass notice: Scope(Class[baseclass]): lsbdistcodename is . notice: Scope(Class[baseclass]): operatingsystem is . notice: Compiled configuration for bptest05.nsd.org in 0.16 seconds So debian.pp and darwin.pp are never getting reached because the include $operatingsystem can''t trigger. $ cat yaml/node/default.yaml --- !ruby/object:Puppet::Node classes: - baseclass name: default names: - default parameters: cn: default ipHostNumber: 10.0.0.0 description: The default node objectClass: - device - ipHost - top - puppetClient puppetClass: baseclass dn: cn=default,ou=Hosts,dc=nsd,dc=org time: 2008-05-20 13:55:03.874776 -07:00 version: 2008-05-20 20:55:03.874906 Z (That looks right to me) $ grep operatingsystem yaml/facts/bptest05.nsd.org.yaml operatingsystemrelease: 2.6.18-6-486 operatingsystem: Debian (Also looks right) What more can I provide? This is happening to the darwin clients as well. Thanks. -- Mark Foster - Sr. Systems Engineer - BitPusher, LLC We push your bits so you don''t have to! http://www.bitpusher.com/ --~--~---------~--~----~------------~-------~--~----~ 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 May 20, 2008, at 4:27 PM, Mark Foster wrote:> I hate to bring this up again but problem of facter vars getting > "lost" > is back. Please let me know if I should file as a bug?It''s filed as #1178: http://reductivelabs.com/trac/puppet/ticket/1178 It''s highest on my priority to fix, but given that I''m at a client site this week and am getting 50 emails a day, that doesn''t mean much. -- SCSI is *not* magic. There are fundamental technical reasons why it is necessary to sacrifice a young goat to your SCSI chain now and then. --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke Kanies wrote:> On May 20, 2008, at 4:27 PM, Mark Foster wrote: > > >> I hate to bring this up again but problem of facter vars getting >> "lost" >> is back. Please let me know if I should file as a bug? >> > > > It''s filed as #1178: http://reductivelabs.com/trac/puppet/ticket/1178 > > It''s highest on my priority to fix, but given that I''m at a client > site this week and am getting 50 emails a day, that doesn''t mean much. > >I believe it''s not the same issue. When I disable LDAP and go back to using nodes.pp with just node default { include baseclass } it "just works" e.g. the facter vars are accessible. There is something wonky about default node in LDAP. I tried the workaround suggested in the ticket 1178 (copying yaml/facts/ around) but that didn''t help. Thanks. -- Mark Foster - Sr. Systems Engineer - BitPusher, LLC We push your bits so you don''t have to! http://www.bitpusher.com/ --~--~---------~--~----~------------~-------~--~----~ 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 May 21, 2008, at 11:10 AM, Mark Foster wrote:> > Luke Kanies wrote: >> On May 20, 2008, at 4:27 PM, Mark Foster wrote: >> >> >>> I hate to bring this up again but problem of facter vars getting >>> "lost" >>> is back. Please let me know if I should file as a bug? >>> >> >> >> It''s filed as #1178: http://reductivelabs.com/trac/puppet/ticket/1178 >> >> It''s highest on my priority to fix, but given that I''m at a client >> site this week and am getting 50 emails a day, that doesn''t mean >> much. >> >> > I believe it''s not the same issue. > When I disable LDAP and go back to using nodes.pp with just > node default { > include baseclass > } > it "just works" e.g. the facter vars are accessible. There is > something > wonky about default node in LDAP. > I tried the workaround suggested in the ticket 1178 (copying yaml/ > facts/ > around) but that didn''t help.Any luck in tracking down what the actual issue is? Shouldn''t be all that hard to experiment with what''s going on; look in indirectory/node/ ldap.rb and see what you can see. -- I am not young enough to know everything. -- Oscar Wilde --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---