Open timspencer opened 8 years ago
@timspencer oh, it's a problem with OpenSSL::SSL::SSLError in your Rails app and probably you want to try a few links below :
http://railsapps.github.io/openssl-certificate-verify-failed.html http://stackoverflow.com/questions/12208110/opensslsslsslerror-certificate-verify-failed
Yes. I know what the error says. That error is not emitted by a rails app, but by chef-client -z while trying to provision a node. The problem is that I don't control softlayer's cert (which may or may not be properly set up), nor do I control the code that calls into net/http (which can be told to ignore ssl verification errors). I was assuming that this was why you were constraining the chef and chef-provisioning gem versions.
My request still stands: Can you update your constraints to modern versions of chef and chef-provisioning and make sure it works? I'm willing to bet that you can do this a lot faster/easier than I can. :-)
@timspencer sure, I will try to get some time this week to upgrade it.
@timspencer before the upgraded version is available, probably you want to restrict your gems in versions like below :
chef (11.16.4) chef-provisioning (0.18) chef-zero (2.2.1) cheffish (0.9.2)
Any progress here? I'd love to help - is there a TODO? :)
@boldandbusted sure, please feel free to make pull request and we can work together on this. Btw, I just updated this driver to 4.0 and will publish it very soon. Probably you can help from there.
@wzymaster Wow, that was fast. Awesome! Do you mind if I also help a bit with the docs?
@boldandbusted Yes, for sure ! Please feel free to let me know what you want to do together.
Hey there! I tried to use this gem, but we are running a later version of chef than what your gem allows. When I removed the constraint from the gem (and a few others, like the ancient chef-provisioning one), I get this:
Not sure if that helps or not, but I wanted to register some interest in getting this code up to date, if possible. Thanks, and have fun!