external_nodes = /etc/puppet/manifests/extdata/getnode
node_terminus = exec
the puppet master complains that it can't find the node for all NON
external nodes. How do I do this in puppet 2.6?
Doug
Yeah. I think I forgot that your supposed to return a blank yaml block
if the external node script can't find the node, which then imforms
puppet to go look at the files. Probably because that's not documented
anywhere. So, I fixed that, and now, I have this in
/etc/puppet/puppet.conf:
external_nodes = /etc/puppet/getnode
node_terminus = exec
and an external node in
/etc/puppet/manifests/extdata/app01.foo.com.yaml, which contains:
---
XXX
classes:
- facility::paloalto
- hardware::vmware
- function::appServer
- elements::tfel0
xenvironment: production
parameters:
node_ldap_groupdn: cn=ops,ou=groups,dc=foo,dc=com
yes, with bogus data. There's an extraneous 'XXX' there and
environment has an 'x' prefixed to the front. Puppet isn't finding it,
it seems because the client is just logging:
Aug 20 20:08:09 s_...@app01.foo.com puppet-agent[14873]: Starting
Puppet client version 2.6.0
Aug 20 20:08:09 s_...@app01.foo.com puppet-agent[14873]: Finished
catalog run in 0.03 seconds
and when I run the script manually, I get:
prov01 /etc/puppet/manifests/extdata:# /etc/puppet/getnode app01.foo.com
---
XXX
classes:
- facility::paloalto
- hardware::vmware
- function::appServer
- elements::tfel0
xenvironment: production
parameters:
node_ldap_groupdn: cn=ops,ou=groups,dc=foo,dc=com
So... something is borked with puppet and I don't know what. *sigh*
Doug.