Failing ENC effort - a little help?

124 views
Skip to first unread message

jblaine

unread,
Aug 22, 2011, 3:28:24 PM8/22/11
to puppet...@googlegroups.com
Master puppet.conf has:
node_terminus = exec
external_nodes = /etc/puppet/hostdb-ENC.py

Master reports:
err: Could not find node 'rcf-cm-test.our.org'; cannot compile

ENC tests fine by my eyes, but perhaps my YAML is invalid?  It tests out fine

Testing the ENC with rcf-cm-test.our.org:
# /etc/puppet/hostdb-ENC.py rcf-cm-test.our.org
---
classes:
- testclass
parameters:
  puppetserver: rcf-cm-master.our.org

#

jblaine

unread,
Aug 22, 2011, 7:51:14 PM8/22/11
to puppet...@googlegroups.com
This is Puppet 2.7.3, FWIW.

As far as I can see, this is really broken somehow.

This ENC below gives the same 'Could not find node' error even when spitting canned
information back:

#!/bin/sh

echo<<END
---
classes:
  - foo
END
exit 0

puppet master --no-daemonize --verbose --debug reports:

debug: Executing '/etc/puppet/hostdb-ENC.sh rcf-cm-test.our.org'
debug: Empty response for rcf-cm-test.our.org from exec exec terminus

Stefan Schulte

unread,
Aug 22, 2011, 8:13:34 PM8/22/11
to puppet...@googlegroups.com

I guess you want to replace "echo" with "cat"?

jblaine

unread,
Aug 22, 2011, 8:20:07 PM8/22/11
to puppet...@googlegroups.com
Indeed.

Now if I could figure out why the simple Python output is rejected from the 1st message.

At least I know *something* functions now though.

jblaine

unread,
Aug 22, 2011, 9:55:42 PM8/22/11
to puppet...@googlegroups.com
Problem solved.  Turns out the Python code was failing only as user puppet because of a
fricking PYTHON_EGG_CACHE directory permission issue, and Puppet was "helpfully" hiding
all details of that until I hacked around in the Puppet source :|
Reply all
Reply to author
Forward
0 new messages