[chef] Re: Question about new client registration for VM

[Dreamcat4 < >]

On Thu, Nov 11, 2010 at 12:14 PM, Dreamcat4 
<
 >
 wrote:
> Hi!
>
> I'm trying to register a Virtual Machine as new node. As we know -
> chef-client sends up the validation.pem to download a new client.pem
> file and register itself as a new node...
>
> An error occurs at the point where the client is expecting to receive
> its new client.pem file from the server:
>
> "/var/lib/gems/1.8/gems/chef-0.9.12/bin/../lib/chef/rest.rb:80:in
> `register': The response from the server did not include a private
> key! (Chef::Exceptions::CannotWritePrivateKey)"
>
> Full log:
> https://gist.github.com/669039
>
>
> Could this be because the chef server thinks the node is already
> registered (because the host node shares the same IP address as the
> Virtual Machine)?

Another thing...

In the mean time (as a work-around) I can create new VM nodes manually
with "knife create client && knife create node".

Then copy over the client.pem file into the Virtual Machine. However
creating a node in that manner seems not to be ideal. All the Ohai
attributes are missing. They are never uploaded / synced to the
chef-server. Only the original attributes get updated (the run_list,
node_name).

However I think thats an entirely different issue to the original
problem. They're missing probably just as only existing json
attributes are being synced / updated. For my manually created nodes -
by default do not start life with the ohai attributes. So no FQDN,
uptime, ohai_time or anything else... :(


Anyway. It would be great to better understand the initial problem
regarding downloading the client.pem. I.e - Whats happening during the
client validation / handshake. However its proving rather tough-going
for me with all that encryption / security stuff going on in there! -
Any help appreciated :)

>
> Regards
>
> dreamcat4
> 
 
>