chef-boneyard / chef-provisioning

A library for creating machines and infrastructures idempotently in Chef.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

fatal: unable to access 'https://github.com/chef/chef-provisioning/': SSL certificate problem: unable to get local issuer certificate

smithapitla opened this issue · comments

I am receiving below error while running chef verify command. Please provide a work around for it.

fatal: unable to access 'https://github.com/chef/chef-provisioning/': SSL certificate problem: unable to get local issuer certificate

Can you please gist a full output?

Please find the full output below.

chef verify
Running verification for component 'berkshelf'
Running verification for component 'test-kitchen'
Running verification for component 'tk-policyfile-provisioner'
Running verification for component 'chef-client'
Running verification for component 'chef-dk'
Running verification for component 'chef-provisioning'
Running verification for component 'chefspec'
Running verification for component 'generated-cookbooks-pass-chefspec'
Running verification for component 'rubocop'
Running verification for component 'fauxhai'
Running verification for component 'knife-spork'
Running verification for component 'kitchen-vagrant'
Running verification for component 'package installation'
Running verification for component 'openssl'
Running verification for component 'inspec'
Running verification for component 'delivery-cli'
Running verification for component 'git'
Running verification for component 'opscode-pushy-client'
Running verification for component 'chef-sugar'
........................................................................../opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/mixlib-shellout-2.2.7/lib/mixlib/shellout.rb:289:in invalid!': Expected process to exit with [0], but received '128' (Mixlib::ShellOut::ShellCommandFailed) ---- Begin output of /opt/chefdk/gitbin/git clone https://github.com/chef/chef-provisioning ---- STDOUT: STDERR: Cloning into 'chef-provisioning'... fatal: unable to access 'https://github.com/chef/chef-provisioning/': SSL certificate problem: unable to get local issuer certificate ---- End output of /opt/chefdk/gitbin/git clone https://github.com/chef/chef-provisioning ---- Ran /opt/chefdk/gitbin/git clone https://github.com/chef/chef-provisioning returned 128 from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/mixlib-shellout-2.2.7/lib/mixlib/shellout.rb:276:in error!'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:128:in block in sh!' from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:128:in tap'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:128:in sh!' from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/command/verify.rb:483:in block (3 levels) in class:Verify'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:165:in block in tmpdir' from /opt/chefdk/embedded/lib/ruby/2.3.0/tmpdir.rb:89:in mktmpdir'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:164:in tmpdir' from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/command/verify.rb:481:in block (2 levels) in class:Verify'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:99:in instance_eval' from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/component_test.rb:99:in run_smoke_test'
from /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-dk-1.2.22/lib/chef-dk/command/verify.rb:586:in `block (2 levels) in invoke_tests'

When I connect to my company VPN, instead of the above error I see the request timeout.

hi smithapitla

  • is there any resolution to this error. Please advise if there is any
  1. Update a CA certs on your local machine by applying a security patches and/or use latest version of ChefDK.
  2. It's not even the place to complain about a timeouts while on VPN to your company, maybe they route all traffic trough the VPN and block anything going out to a public entity.