I have a very basic puppet install right now, running puppet master, with the dashboard and foreman on the same host, I have some legacy static nodes (nodes.pp) and now I am using puppet to provision nodes in EC2. I am running cloud provisioner .60rc1 and my question is what happens after a puppet node bootstrap? I'm running into some issues and maybe its just idiot user driving this thing, but I do something like:
puppet node bootstrap --image ami-79e32e10 --keypair puppet --login root --keyfile \ /root/.ssh/puppet.pem --certname app01.c43870.blueboxgrid.com --type m1.small which works okay when EC is being nice, the node comes up and puppet logs in and installs the agent which then generates a certificate and has it auto signed. After which the puppet agent exits (why?), and nobody is really happy after that: Sep 30 12:16:51 app01 puppet-master[18203]: Removing file Puppet::SSL::CertificateRequest 21b5041a-db2a-f26f-c2e6-faf3676a5d2a at '/etc/puppet/ssl/ca/requests/21b5041a-db2a-f26f-c2e6- faf3676a5d2a.pem' Sep 30 12:17:01 app01 puppet-master[18203]: Could not find node '21b5041a-db2a-f26f-c2e6-faf3676a5d2a'; cannot compile What am I missing? Of course there's no catalog, I had no idea what the name of the node was going to appear as, so its not like I could put together a manifest for new instance. Is the idea being that it gets a default set of packages then I need to use facts to figure out what it is? So basically my question is, what happens next? What am I missing? I have a new instance with puppet on it but since there's no catalog, the agent (if it were still running) wouldn't know what to ask for. Thanks -Josh -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
