simonjohansson
commented
11 years ago After doing some digging in the source ive discovered where the whole thing crashes. (Im not a ruby-dev so Im in deep water right now)
In /.vagrant.d/gems/gems/berkshelf-1.4.4/lib/berkshelf/locations/chef_api_locations.rb line 135.
@conn = Ridley.new(
server_url: uri,
client_name: node_name,
client_key: client_key,
ssl: {
verify: options[:verify_ssl]
}
)Doing some debugging priting of uri, node_name, client_key and options[:verify_ssl] before createing the connection with Ridley reveals
uri, http://supersecret-url:4000
node_name, simon
client_key, /home/simon/.chef/key.pem
ssl, trueSo up to this point everything seems to work like it should, but then BAM, I get the stacktrace posted in the first message
Interestingly though.
simon@simonpad ~$ irb
irb(main):001:0> require 'ridley'
=> true
irb(main):002:0> Ridley.new(server_url: 'http:///supersecret-url:4000', client_name:'simon', client_key:'/home/simon/.chef/key.pem', ssl: {verify: true})
=> #<Celluloid::ActorProxy(Ridley::Client:0x1e72c2c) @options={:ssh=>{}....................................................................I get a connection
ivey
adamjk-dev
reset
dustinmm80
maraca
tmatilai
iroller
Versions:
To make sure that there is not weird state going on, I start out removing the berkshelf directory
I have a berksfile that looks like this
Doing a vagrant up/provision in the cookbook works as expected. It pulls in all the cookbooks and provisions the machine etc.
I then add a new cookbook that needs to be fetched from my chef-server into the berksfile like so,
and run berks to pull in base, and all the cookbooks that base depend upon, which works fine. (note that I dont have a config.json in ~/.berkshelf or in the cookbook directory)
But when running a vagrant provision it yields this:
Creating a config.json in ~/.berkshelf via berks configure so it looks like this
doesnt help either.
But by removing the last line in the Berksfile, everything works as expected again, including using the base cookbook.