Skip to content
This repository was archived by the owner on Jul 14, 2021. It is now read-only.

0.2.2 knife still uses 12.0.0.alpha.1 #162

Closed
jf647 opened this issue Sep 17, 2014 · 2 comments
Closed

0.2.2 knife still uses 12.0.0.alpha.1 #162

jf647 opened this issue Sep 17, 2014 · 2 comments

Comments

@jf647
Copy link

jf647 commented Sep 17, 2014

This is with the MacOS ChefDK hitting Enterprise Chef 11.1.3.

After nuking /opt/chefdk and ~/.gem and installing ChefDK 0.2.2, chef and knife are still using 12.0.0.alpha.1 of the gem:

~  which ruby
/opt/chefdk/embedded/bin/ruby
➜  ~  ruby -v
ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin12.0]
➜  ~  gem list chef

*** LOCAL GEMS ***

chef (12.0.0.alpha.1, 11.16.0)
chef-dk (0.2.2)
chef-vault (2.2.1)
chef-zero (2.2, 1.5.6)
chefspec (4.0.1)
➜  ~  knife cookbook list
ERROR: The data in your request was invalid
Response: {"error": "400 - Bad Request: Chef Client version between 10 and  11" required. Your version of Chef is 12.0.0.alpha.1."}
➜  ~  knife -v
Chef: 12.0.0.alpha.1
➜  ~  gem which chef
/opt/chefdk/embedded/lib/ruby/gems/2.1.0/gems/chef-12.0.0.alpha.1/lib/chef.rb
➜  ~
@irvingpop
Copy link

Hi, can you please try /opt/chefdk/bin/knife --version instead?

@lamont-granquist
Copy link
Contributor

You need to take /opt/chefdk/embedded/bin out of your path or put /opt/chefdk/bin first, or use the chef shell-init command properly. See #163

@chef-boneyard chef-boneyard locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

3 participants