After investigating further I've found this: When commenting out the environment stanza the puppet.conf file (in my case the "testing" environment), everything seems ok wrt (amongs others) these variables:
[r...@puppetmaster tmp]# puppetmasterd --no-daemonize --configprint all|egrep -i 'external|vardir|logdir|rundir' external_nodes = /usr/bin/python /etc/puppet/tools/extlookup-satellite.py logdir = /var/log/puppet rundir = /var/run/puppet vardir = /var/lib/puppet When uncommenting the environement stanza, not only does the "external_nodes" variable change, but also the variables defined in the "main" stanza in puppet.conf: [r...@puppetmaster tmp]# puppetmasterd --no-daemonize --configprint all|egrep -i 'external|vardir|logdir|rundir' external_nodes = none logdir = /var/puppet/log rundir = /var/puppet/run vardir = /var/puppet So it looks like puppetmaster simply bypass the whole puppet.conf file (or at least the "main" and "puppetmasterd" stanzas). Any clues as to why the puppetmaster would skip the puppet.conf file? It seems possible that it performs some sort of syntax or semtatics check of some kind before it decides to bypass the file and go with other (default?) values, but if so I have noe clue on where the bug might be. - Kenneth On Tue, Jul 13, 2010 at 9:55 AM, Kenneth Holter <[email protected]> wrote: > I've pasted the output of the suggested commands here: > http://pastebin.com/npd6akwY > > I noticed that configprint shows that "extrenal_nodes" gets set to > "none" as soon as I uncomment one of the environments (in this case > "testing"). Is there any dependencies or something that the > puppetmaster checks for with regards to environments, which may > explain this behavior? > > Btw, I verified that the client picks up the correct environment when > using the "--environment=<environments>" flag. And also, I restart the > puppetmaster frequently when debugging this, so I don't believe #3580 > bug applies to me. > > > - Kenneth > > On Mon, Jul 12, 2010 at 7:40 PM, Nan Liu <[email protected]> wrote: >> On Jul 12, 2010, at 8:30 AM, Kenneth Holter <[email protected]> wrote: >> >> I moved the "environments=testing" from "main" to "puppetmasterd", >> >> restarted puppetmaster, and tried another puppet client run. Same >> >> results. Even tried without that entry, still don't work. >> >> What I meant was >> [main] >> ... >> environment=testing >> >> [puppetmasterd] >> ... >> environments=production,testing >> >> I found a thread indicating that the site.pp file should contain a >> >> default node, so I included this in /etc/puppet/manifests/site.pp: >> >> -- code start -- >> >> node default { >> >> info("default node") >> >> } >> >> -- code end -- >> >> ..and found that this is being parsed instead of puppetmaster fetching >> >> the node information externally via the external nodes script. Any >> >> ideas on how to proceed debugging this? >> >> >> I would run "puppetd --configprint environment" to see what's the real >> configuration after parsing. If it's setting it to the testing >> environment but not invoking external node, please run "puppetd >> --configprint all | grep ldap" and forward a copy of the output. >> >> If it's a bug, definitely worth looking into and confirming. >> >> Thanks, >> >> Nan >> >> Sent from my iPhone >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Puppet Users" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/puppet-users?hl=en. >> > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
