Fresh chef solo environment

[locochris]

ie. a fix for gusteau not being able to use chef-solo on an existing VM.

ie. a fix for:

*** [2013-07-12T14:40:13] GUSTEAU: 192.168.100.30> chef-solo -c /etc/chef/solo.rb -j /etc/chef/dna.json --color
/opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:247:in `to_specs': Could not find chef (>= 0) amongst [activesupport-4.0.0, atomic-1.1.10, bundler-1.3.5, bundler-unload-1.0.1, chronic-0.9.1, god-0.13.2, i18n-0.6.4, kgio-2.8.0, minitest-4.7.5, multi_json-1.7.7, rack-1.5.2, raindrops-0.11.0, rake-10.1.0, rubygems-bundler-1.2.2, rvm-1.11.3.8, thread_safe-0.1.0, tzinfo-0.3.37, unicorn-4.6.3, whenever-0.8.3] (Gem::LoadError)
    from /opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:256:in `to_spec'
    from /opt/chef/embedded/lib/ruby/site_ruby/1.9.1/rubygems.rb:1231:in `gem'
    from /usr/bin/chef-solo:22:in `<main>'
ERROR: [2013-07-12T14:40:13] GUSTEAU:   192.168.100.30> chef-solo -c /etc/chef/solo.rb -j /etc/chef/dna.json --color

[coveralls]

Coverage increased (+0%) when pulling 53a7e57 on fresh_chef_solo_environment into f7c35f5 on master.

[ghost]

A less intrusive approach would be unsetting GEM_PATH and GEM_HOME, see http://tickets.opscode.com/browse/CHEF-3581. Could you try it this way first?

[locochris]

cc @simi (who seems to have had the same trouble)

Yes running chef-solo without GEM_HOME and GEM_PATH works too. :)

[simi]

Where I mentioned it @locochris ?

[coveralls]

Coverage increased (+0%) when pulling 76d599d on fresh_chef_solo_environment into f3059d4 on master.

[ghost]

Looks good to me

[locochris]

Ahh great. So time for a new release? :)