Skip to content

metal binary complains about private key #65

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
mwrock opened this issue May 28, 2014 · 6 comments
Closed

metal binary complains about private key #65

mwrock opened this issue May 28, 2014 · 6 comments
Labels
Type: Bug Doesn't work as expected.
Milestone

Comments

@mwrock
Copy link
Contributor

mwrock commented May 28, 2014

working off of the beta.5 bits, if I run:

metal destroy QA1T3NDEVOPSLABCHEF01

I receive this error:

[2014-05-28T13:43:09-07:00] INFO: Starting chef-zero on port 8889 with repository at repository at /home/mwrock/dev/DevOps/chef-repo
  One version per cookbook

{:chef_server_url=>"http://127.0.0.1:8889", :options=>{:client_name=>"mwrock", :signing_key_filename=>"/home/mwrock/dev/DevOps/chef-repo/.chef/mwrock.pem"}}
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/mixlib-authentication-1.3.0/lib/mixlib/authentication/signedheaderauth.rb:94:in `private_encrypt': private key needed. (OpenSSL::PKey::RSAError)

Note that

{:chef_server_url=>"http://127.0.0.1:8889", :options=>{:client_name=>"mwrock", :signing_key_filename=>"/home/mwrock/dev/DevOps/chef-repo/.chef/mwrock.pem"}}

is output I hacked in to see the server info.

I'm still figuring my way around chef keys but the above key mwrock.pem is a key that is in my knife.rb and configured for an actual chef server. Should a chef-zero run ignore that key?

Thanks!

@jkeiser
Copy link
Contributor

jkeiser commented May 28, 2014

The client doesn't ignore the key if you specify it--do you have a ~/.chef/knife.rb, or a .chef/knife.rb in the repository you are presently working in?

@mwrock
Copy link
Contributor Author

mwrock commented May 29, 2014

the key is specified in .chef/knife.rb in my repo. I'd like to keep it there for other purposes. However I routinely use chef-zero via chef-client -z and never have this issue.

@jkeiser
Copy link
Contributor

jkeiser commented May 29, 2014

Yeah, it certainly shouldn't be happening--I'm not sure at the moment what could be causing it. I iwould have expected the file to get loaded just like normal in the metal executable.

@jkeiser
Copy link
Contributor

jkeiser commented May 29, 2014

(chef-client -z is likely loading the .pem as well.)

@jkeiser jkeiser added the bug label May 31, 2014
@jkeiser jkeiser added this to the 1.0 milestone Aug 19, 2014
@jkeiser jkeiser modified the milestones: Later, 1.0 Nov 6, 2014
@randomcamel
Copy link
Contributor

@mwrock Both chef-provisioning and chef-client have come a long way: is this still an issue?

@mwrock
Copy link
Contributor Author

mwrock commented Jul 26, 2015

Wow yeah. It has been a while. Just looked at this again and it looks like metal is no longer included in the gemspec's executables as of 37ec6ea so its no longer available at the commandline. I'm gonna close this since it appears this has been abandoned.

@mwrock mwrock closed this as completed Jul 26, 2015
@tas50 tas50 added Type: Bug Doesn't work as expected. and removed Bug labels Jul 31, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Doesn't work as expected.
Development

No branches or pull requests

4 participants