You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I went to remove the SHA1-pinned vagabond line in my Gemfile with just "gem 'vagabond'", hoping to just use the main Vagabond gem, but I'm getting odd errors. See below...
jpipes@uberbox:~/repos/att-cloud/cookbook-infra-db$ bundle exec vagabond status
[sudo] password for jpipes:
Name State PID IP
metering_master N/A N/A N/A
metering_slave N/A N/A N/A
pxc_one N/A N/A N/A
pxc_three N/A N/A N/A
pxc_two N/A N/A N/A
server N/A N/A N/A
jpipes@uberbox:~/repos/att-cloud/cookbook-infra-db$ vv Gemfile
jpipes@uberbox:~/repos/att-cloud/cookbook-infra-db$ bundle update
Fetching gem metadata from https://rubygems.org/........
Fetching gem metadata from https://rubygems.org/..
Using i18n (0.6.5)
Installing multi_json (1.8.2)
Installing activesupport (3.2.15)
Using addressable (2.3.5)
Using builder (3.2.2)
Using gyoku (1.1.0)
Installing mini_portile (0.5.2)
Installing nokogiri (1.6.0) with native extensions
Using akami (1.2.0)
Using archive-tar-minitar (0.5.2)
Using hashie (2.0.5)
Installing attribute_struct (0.1.8)
Using buff-ruby_engine (0.1.0)
Installing buff-shell_out (0.1.1)
Using chozo (0.6.1)
Using multipart-post (1.2.0)
Using faraday (0.8.8)
Using minitar (0.5.4)
Using rbzip2 (0.2.0)
Using retryable (1.3.3)
Using buff-extensions (0.5.0)
Using varia_model (0.2.0)
Using buff-config (0.4.0)
Using buff-ignore (1.1.0)
Using timers (1.1.0)
Using celluloid (0.14.1)
Using nio4r (0.5.0)
Using celluloid-io (0.14.1)
Using erubis (2.7.0)
Using json (1.7.7)
Using mixlib-log (1.6.0)
Using mixlib-authentication (1.3.0)
Using net-http-persistent (2.9)
Installing net-ssh (2.7.0)
Using solve (0.8.1)
Installing ffi (1.9.3) with native extensions
Using gssapi (1.0.3)
Installing httpclient (2.3.4.1)
Using little-plugger (1.1.3)
Installing logging (1.8.1)
Using rubyntlm (0.1.1)
Using rack (1.5.2)
Using httpi (0.9.7)
Using nori (1.1.5)
Using wasabi (1.0.0)
Using savon (0.9.5)
Using uuidtools (2.1.4)
Installing winrm (1.1.3)
Installing ridley (1.5.3)
Using thor (0.18.1)
Using berkshelf (2.0.10)
Using buff-platform (0.1.0)
Installing highline (1.6.20)
Using mixlib-cli (1.3.0)
Installing mixlib-config (2.0.0)
Using mixlib-shellout (1.2.0)
Using net-ssh-gateway (1.2.0)
Using net-ssh-multi (1.1)
Using ipaddress (0.8.0)
Using systemu (2.5.2)
Using yajl-ruby (1.1.0)
Installing ohai (6.20.0)
Installing mime-types (2.0)
Using rest-client (1.6.7)
Using chef (11.4.4)
Using multi_xml (0.5.5)
Using httparty (0.11.0)
Using fauxhai (1.1.1)
Using ci_reporter (1.9.0)
Using minitest (4.7.5)
Using minitest-chef-handler (1.0.1)
Installing rspec-core (2.14.7)
Installing diff-lcs (1.2.5)
Installing rspec-expectations (2.14.4)
Installing rspec-mocks (2.14.4)
Using rspec (2.14.1)
Using chefspec (1.3.1)
Installing elecksee (1.0.16)
Installing foodcritic (0.2.0)
Installing net-sftp (2.1.2)
Installing knife-bootstrapsync (1.0.2)
Using librarian (0.1.1)
Installing librarian-chef (0.0.2)
Using net-scp (1.1.2)
Installing safe_yaml (0.9.7)
Installing serverspec (0.11.4)
Using strainer (3.3.0)
Installing test-kitchen (1.0.0.beta.4)
Installing vagabond (0.2.10)
Using bundler (1.2.3)
Your bundle is updated! Use `bundle show [gemname]` to see where a bundled gem is installed.
jpipes@uberbox:~/repos/att-cloud/cookbook-infra-db$ bundle exec vagabond status
Fetching required cookbooks...
-> COMPLETE!
Ensuring expected system state (creating required base containers)
- This can take a while on first run or new templates...
Expected process to exit with [0], but received '1'
---- Begin output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
STDOUT:
STDERR: /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:90:in `block in materialize': Could not find i18n-0.6.5 in any of the sources (Bundler::GemNotFound)
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `map!'
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `materialize'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:113:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:158:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:147:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:23:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:11:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:116:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:17:in `<top (required)>'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
Ran sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb returned 1
-> FAILED!
Vagabond error encountered. Exiting: Expected process to exit with [0], but received '1'
---- Begin output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
STDOUT:
STDERR: /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:90:in `block in materialize': Could not find i18n-0.6.5 in any of the sources (Bundler::GemNotFound)
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `map!'
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `materialize'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:113:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:158:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:147:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:23:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:11:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:116:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:17:in `<top (required)>'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
Ran sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb returned 1
jpipes@uberbox:~/repos/att-cloud/cookbook-infra-db$ rm -rf .vagabond/
jpipes@uberbox:~/repos/att-cloud/cookbook-infra-db$ bundle exec vagabond status
Fetching required cookbooks...
-> COMPLETE!
Ensuring expected system state (creating required base containers)
- This can take a while on first run or new templates...
Expected process to exit with [0], but received '1'
---- Begin output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
STDOUT:
STDERR: /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:90:in `block in materialize': Could not find i18n-0.6.5 in any of the sources (Bundler::GemNotFound)
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `map!'
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `materialize'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:113:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:158:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:147:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:23:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:11:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:116:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:17:in `<top (required)>'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
Ran sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb returned 1
-> FAILED!
Vagabond error encountered. Exiting: Expected process to exit with [0], but received '1'
---- Begin output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
STDOUT:
STDERR: /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:90:in `block in materialize': Could not find i18n-0.6.5 in any of the sources (Bundler::GemNotFound)
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `map!'
from /usr/lib/ruby/vendor_ruby/bundler/spec_set.rb:83:in `materialize'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:113:in `specs'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:158:in `specs_for'
from /usr/lib/ruby/vendor_ruby/bundler/definition.rb:147:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/environment.rb:23:in `requested_specs'
from /usr/lib/ruby/vendor_ruby/bundler/runtime.rb:11:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler.rb:116:in `setup'
from /usr/lib/ruby/vendor_ruby/bundler/setup.rb:17:in `<top (required)>'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'
---- End output of sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb ----
Ran sudo bundle exec chef-solo -j /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/dna.json -c /home/jpipes/repos/att-cloud/cookbook-infra-db/.vagabond/solo.rb returned 1
My updated Gemfile.lock is here, if that is useful:
It's failing to find a gem within the bundle (i18n) but it is getting installed via the bundle update. Do you have multiple rubies on the system, or an omnibus chef install? Is the bundle vendored or being installed into the system gems, or being installed to the user's GEM_HOME? If they aren't being vendored it might be worthwhile to vendor them to a local path:
$ bundle install --path ./vendor
and then give it a run again. Let me know what you get! :)
Hi Chris, hope all is well...
Recently I went to remove the SHA1-pinned vagabond line in my Gemfile with just "gem 'vagabond'", hoping to just use the main Vagabond gem, but I'm getting odd errors. See below...
I changed this line in my Gemfile:
to just:
My updated Gemfile.lock is here, if that is useful:
Any ideas?
The text was updated successfully, but these errors were encountered: