Small correction: "if I edit the host via Foreman web interface, I can't no longer see it from "curl -k https://foreman/node/nodename?format=yml";; I'd get message "404 Not Found" from the command line" --> I'd have to re- run puppetd -t, to be able to get a result from "curl -k https://foreman/node/nodename?format=yml"; again.. after that --> I'd have two nodes of the same name listed in Foreman web interface..
On Jul 23, 7:14 am, CraftyTech <[email protected]> wrote: > Thanks for the reply Ohad. Actually, that's part of the issue as > well; If I edit the host via Foreman web interface, I can't no longer > see it from "curl -khttps://foreman/node/nodename?format=yml";; I'd > get message "404 Not Found" from the command line. On the flip side, > I'd have two nodes of the same name listed in Foreman web interface; > 1) A new one that get's created when I run puppetd -t, and 2) The one > that I edited via the web interface.... I know it sounds confusing, > but that's exactly what's happening... It seems that the foreman > environment, and puppet environment see two different nodes, even > thought there's only one host.yaml file.. > > On Jul 23, 1:46 am, Ohad Levy <[email protected]> wrote: > > > > > Hi, > > > The output you get from external nodes means that the host was not allocated > > to any class or puppet environment, make sure you edit the host details > > first in foreman. > > > Ohad > > > On Fri, Jul 23, 2010 at 4:22 AM, CraftyTech <[email protected]> wrote: > > > Hello All, > > > > So I finally got around to start to cut over node definitions > > > from standard flat files to external nodes (foreman), and getting > > > error message: "Error 400 on SERVER: Could not find node 'nodename'; > > > cannot compile" - So basically it can't pick up the node from the > > > external node config. > > > > When I test the fetching of the yaml file it seems to work as I get a > > > result back: i.g: > > > curl -khttps://foreman/node/nodename?format=yml > > > > --- > > > parameters: > > > puppetmaster: puppet > > > classes: [] > > > > environment: "" > > > > ########################################################################### > > > ################### > > > This is my puppet.conf: > > > > [main] > > > vardir = /var/lib/puppet > > > logdir = /var/log/puppet > > > rundir = /var/run/puppet > > > reports= log,foreman,rrdgraph,store > > > clientyamldir = /var/lib/puppet/yaml/node > > > pluginsync = true > > > external_nodes = /etc/puppet/external_node.rb > > > node_terminus = exec > > > > [puppetmasterd] > > > ssl_client_header = SSL_CLIENT_S_DN > > > ssl_client_verify_header = SSL_CLIENT_VERIFY > > > modulepath = $confdir/modules > > > templatedir = /etc/puppet/manifests/templates > > > #clientyamldir = /var/lib/puppet/yaml/node > > > reportdir = /var/lib/puppet/reports > > > storeconfigs = true > > > dbadapter = mysql > > > dbuser = app_puppet > > > dbpassword = xxxxxxxxxxxxxx > > > dbserver = localhost > > > dbsocket = /sql/mysql/mysql.sock > > > rrddir = /var/lib/puppet/rrd > > > rrdinterval = $runinterval > > > rrdgraph = true > > > > [puppetd] > > > classfile = $vardir/classes.txt > > > report = true > > > localconfig = $vardir/localconfig > > > > Any ideas? > > > > Thanks, > > > > Henry > > > > -- > > > 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]<puppet-users%2bunsubscr...@google > > > groups.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 [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.
