Failing EC2 agent's ENC lookup, by hand works fine?

asked 2012-12-18 11:55:43 -0500

jblaine gravatar image

updated 2012-12-18 12:56:12 -0500

Is there some trick to EC2/AWS and the Puppet Dashboard ENC?

/etc/puppet/puppet.conf on master:

[master]
# These are needed when the puppetmaster is run by passenger
# and can safely be removed if webrick is used.
ssl_client_header = SSL_CLIENT_S_DN
ssl_client_verify_header = SSL_CLIENT_VERIFY
autosign = true
node_terminus = exec
external_nodes = /usr/bin/env PUPPET_DASHBOARD_URL=http://localhost:3000 
/usr/share/puppet-dashboard/bin/external_node

So we bootstrap a new instance:

master$ sudo RUBYLIB=/etc/puppet/modules/cloud_provisioner/lib puppet 
node_aws bootstrap --group=hadoop-nodes --keyname=jblaine 
--image=ami-3d4ff254 --type=t1.micro --puppet-version=2.7.20-1puppetlabs1 
--login=ubuntu --keyfile=/home/jblaine/.ssh/jblaine-bld.pem 
--server=REDACTED --node-group ...
(more)
edit retag flag offensive close merge delete

Comments

1

Seems one has to restart both the puppetmaster **and puppet-dashboard** services after adding the definition for *external_nodes* and *node_terminus* to /etc/puppet/puppet.conf. That solved it finally for me at least.

jblaine gravatar imagejblaine ( 2012-12-18 14:20:19 -0500 )edit