CloudPack's "node install ...." ignores certname

15 views
Skip to first unread message

Hamoun gh

unread,
Sep 21, 2011, 5:13:01 PM9/21/11
to puppet...@googlegroups.com
although in cloudpack.rb::install(...) user specified certname is
supprted (i.e. options[:certname] ||= Guid.new.to_s), the certname is
not passed to the method when supplied through command line.

any idea?
tx

Dan Bode

unread,
Sep 21, 2011, 5:37:09 PM9/21/11
to puppet...@googlegroups.com
We recently noticed the same issue. I have a feeling that is may be related to the version of puppet that is running. What version are you running? We have actually been actively working on a fix in the following pull request:

https://github.com/puppetlabs/puppetlabs-cloud-provisioner/pull/16

a fix should be available in master soon


--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To post to this group, send email to puppet...@googlegroups.com.
To unsubscribe from this group, send email to puppet-users...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.




--
"Join us for PuppetConf, September 22nd and 23rd in Portland, OR."

hamoun

unread,
Sep 22, 2011, 8:53:50 AM9/22/11
to Puppet Users
tx for the reply. I am using 2.7.3. maybe I should switch to 2.7.4rc3?
the reason I want to pass certname is that, I want to add the node's
config to site.pp right before it can grab its catalog (im using
autosigning).
the other approach was to get the GUID from "install", make the client
wait, add the entry to site.pp based on client generated GUID, then
sign the certificate.
However, I found that even the second method requires changing
cloudpack (i.e. the "init" action does not exactly do this).

Hamoun
> "Join us for PuppetConf <http://bit.ly/puppetconfsig>, September 22nd and
> 23rd in Portland, OR."
>  <http://bit.ly/puppetconfsig>
Reply all
Reply to author
Forward
0 new messages