Chef 0.10 RC with Vagrant (0.7.3)

Chef Infra (archive)
1

Hi,
I’m running into issues with Chef 0.10.0rc.0

I use this vagrant file:

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:

Appreciate any hints or tips.

–
πόλλ’ οἶδ ἀλώπηξ, ἀλλ’ ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

2

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

Appreciate any hints or tips.

the workaround is to mount these fodlers onto your local cookbooks and
site-cookbooks floders:

config.vm.define :chef do |csc|

csc.vm.share_folder("chef-cookbooks-0",
"/tmp/vagrant-chef/cookbooks-0", "#{@cs_kitchen}/site-cookbooks" )
csc.vm.share_folder("chef-cookbooks-1",
"/tmp/vagrant-chef/cookbooks-1", "#{@cs_kitchen}/cookbooks" )
end
Then things proceed to this error:

Any thoughts?

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

3

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

Appreciate any hints or tips.

the workaround is to mount these fodlers onto your local cookbooks and
site-cookbooks floders:

config.vm.define :chef do |csc|

csc.vm.share_folder("chef-cookbooks-0",
"/tmp/vagrant-chef/cookbooks-0", "#{@cs_kitchen}/site-cookbooks" )
csc.vm.share_folder("chef-cookbooks-1",
"/tmp/vagrant-chef/cookbooks-1", "#{@cs_kitchen}/cookbooks" )
end
Then things proceed to this error:

Vagrantfile · GitHub

Any thoughts?

OK I'm not sure this is the cause, but it seems there are problems in
this commit to the 0.10.rc.0 branch of Opscodes Cookbooks:

It looks like an incomplete merge got pushed.

Is there another cookbooks repo we should be tracking for Chef
0.10.rc.0 related changes?

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

4

On Sun, Apr 24, 2011 at 12:42 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

Appreciate any hints or tips.

the workaround is to mount these fodlers onto your local cookbooks and
site-cookbooks floders:

config.vm.define :chef do |csc|

csc.vm.share_folder("chef-cookbooks-0",
"/tmp/vagrant-chef/cookbooks-0", "#{@cs_kitchen}/site-cookbooks" )
csc.vm.share_folder("chef-cookbooks-1",
"/tmp/vagrant-chef/cookbooks-1", "#{@cs_kitchen}/cookbooks" )
end
Then things proceed to this error:

Vagrantfile · GitHub

Any thoughts?

OK I'm not sure this is the cause, but it seems there are problems in
this commit to the 0.10.rc.0 branch of Opscodes Cookbooks:

Refactoring chef -> chef-server cookbook · chef-boneyard/cookbooks@dd3ab7b · GitHub

It looks like an incomplete merge got pushed.

That is a fair sized commit, just search for 'HEAD' and you'll see what I mean.

Is there another cookbooks repo we should be tracking for Chef
0.10.rc.0 related changes?

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

5

On Sunday, April 24, 2011 at 3:14 AM, Hedge Hog wrote:
On Sun, Apr 24, 2011 at 12:42 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

This is caused by either:

  1. Your cookbook_path config setting is empty
    or
  2. Your cookbook_path doesn't have a directory named cookbooks in it.

#2 Seems designed to install the remote cookbooks into your "cookbooks" directory if you have both "cookbooks" and "site-cookbooks" configured in your cookbook_path but obviously both the implementation and the error messaging could be improved.

--
Dan DeLeo

6

On Thu, Apr 28, 2011 at 3:22 PM, Daniel DeLeo dan@kallistec.com wrote:

On Sunday, April 24, 2011 at 3:14 AM, Hedge Hog wrote:

On Sun, Apr 24, 2011 at 12:42 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

This is caused by either:

  1. Your cookbook_path config setting is empty
    or
  2. Your cookbook_path doesn't have a directory named cookbooks in it.
    #2 Seems designed to install the remote cookbooks into your "cookbooks"
    directory if you have both "cookbooks" and "site-cookbooks" configured in
    your cookbook_path but obviously both the implementation and the error
    messaging could be improved.

The Chef Error messaging I think was fine in this case, I think the
issue with the cookbooks-{0,1} is Vagrants - however this all ran OK
under Chef 0.9.12.
But when I get vagrant to mount the /tmp/vagrant-chef/cookbooks-* all
porceeds to the next error I reported, I'm about to check if that is
caused by the opscode/cokkbooks 0.10.rc.0 snafu discussed and fixed on
IRC earlier today.... will report back

--
Dan DeLeo

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

7

On Thu, Apr 28, 2011 at 5:50 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Thu, Apr 28, 2011 at 3:22 PM, Daniel DeLeo dan@kallistec.com wrote:

On Sunday, April 24, 2011 at 3:14 AM, Hedge Hog wrote:

On Sun, Apr 24, 2011 at 12:42 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

This is caused by either:

  1. Your cookbook_path config setting is empty
    or
  2. Your cookbook_path doesn't have a directory named cookbooks in it.
    #2 Seems designed to install the remote cookbooks into your "cookbooks"
    directory if you have both "cookbooks" and "site-cookbooks" configured in
    your cookbook_path but obviously both the implementation and the error
    messaging could be improved.

The Chef Error messaging I think was fine in this case, I think the
issue with the cookbooks-{0,1} is Vagrants - however this all ran OK
under Chef 0.9.12.
But when I get vagrant to mount the /tmp/vagrant-chef/cookbooks-* all
porceeds to the next error I reported, I'm about to check if that is
caused by the opscode/cokkbooks 0.10.rc.0 snafu discussed and fixed on
IRC earlier today.... will report back

with chef 0.10.0.rc.1 and the fixed opscode/cookbooks repo the same
error persists:

[chef] [Thu, 28 Apr 2011 04:52:33 -0700] DEBUG: Re-raising exception:
Errno::EISDIR - link[/etc/chef/webui.rb]
(chef-server::rubygems-install line 119) had an error: Is a directory

  • /etc/chef/webui.rb

Does any one have a recommended workaround?

--
Dan DeLeo

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

8

On Thu, Apr 28, 2011 at 11:11 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Thu, Apr 28, 2011 at 5:50 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Thu, Apr 28, 2011 at 3:22 PM, Daniel DeLeo dan@kallistec.com wrote:

On Sunday, April 24, 2011 at 3:14 AM, Hedge Hog wrote:

On Sun, Apr 24, 2011 at 12:42 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

This is caused by either:

  1. Your cookbook_path config setting is empty
    or
  2. Your cookbook_path doesn't have a directory named cookbooks in it.
    #2 Seems designed to install the remote cookbooks into your "cookbooks"
    directory if you have both "cookbooks" and "site-cookbooks" configured in
    your cookbook_path but obviously both the implementation and the error
    messaging could be improved.

The Chef Error messaging I think was fine in this case, I think the
issue with the cookbooks-{0,1} is Vagrants - however this all ran OK
under Chef 0.9.12.
But when I get vagrant to mount the /tmp/vagrant-chef/cookbooks-* all
porceeds to the next error I reported, I'm about to check if that is
caused by the opscode/cokkbooks 0.10.rc.0 snafu discussed and fixed on
IRC earlier today.... will report back

with chef 0.10.0.rc.1 and the fixed opscode/cookbooks repo the same
error persists:

[chef] [Thu, 28 Apr 2011 04:52:33 -0700] DEBUG: Re-raising exception:
Errno::EISDIR - link[/etc/chef/webui.rb]
(chef-server::rubygems-install line 119) had an error: Is a directory

  • /etc/chef/webui.rb

Does any one have a recommended workaround?

Still failing but with some progress with the 0.10.rc.2 release and
Virtualbox 4.0.6:

$ less /var/log/chef/server-webui.log
merb : chef-server-webui : worker (port 4040) ~ Starting Thin at port 4040
merb : chef-server-webui : worker (port 4040) ~ Using Thin adapter on
host 0.0.0.0 and port 4040.
merb : chef-server-webui : worker (port 4040) ~ Successfully bound to port 4040
merb : chef-server-webui : worker (port 4040) ~ Changing privileges to chef:chef
merb : chef-server-webui : worker (port 4040) ~ Started request
handling: Sat Apr 30 01:09:06 -0700 2011
merb : chef-server-webui : worker (port 4040) ~ Params:
{"action"=>"index", "controller"=>"nodes"}
merb : chef-server-webui : worker (port 4040) ~ I cannot read
/etc/chef/webui.pem, which you told me to use to sign requests! -
(Chef::Exceptions::PrivateKeyMissing)
/usr/lib/ruby/gems/1.8/gems/chef-0.10.0.rc.2/lib/chef/rest/auth_credentials.rb:62:in
load_signing_key' /usr/lib/ruby/gems/1.8/gems/chef-0.10.0.rc.2/lib/chef/rest/auth_credentials.rb:33:in initialize'

The permissions are (600):
$ ls -la /etc/chef/webui.pem
-rw------- 1 vagrant vagrant 1679 2011-04-30 00:17 /etc/chef/webui.pem

I've tried chown chef:chef, and in case this was not a SSH style
permissions issue, I tried various chmod's to no avail.

Any suggestions?

--
Dan DeLeo

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

9

On Sat, Apr 30, 2011 at 6:24 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Thu, Apr 28, 2011 at 11:11 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Thu, Apr 28, 2011 at 5:50 PM, Hedge Hog hedgehogshiatus@gmail.com wrote:

On Thu, Apr 28, 2011 at 3:22 PM, Daniel DeLeo dan@kallistec.com wrote:

On Sunday, April 24, 2011 at 3:14 AM, Hedge Hog wrote:

On Sun, Apr 24, 2011 at 12:42 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 4:45 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

On Fri, Apr 22, 2011 at 3:26 PM, Hedge Hog hedgehogshiatus@gmail.com
wrote:

Hi,
I'm running into issues with Chef 0.10.0rc.0

I use this vagrant file:
Chef 0.10.0.rc.0 · GitHub

I repackage my Vagrant base box after updating it with:
sudo gem install chef --pre --no-ri --no-rdoc

On running vagrant up chef I get the error shown in the gist:
Chef 0.10.0.rc.0 · GitHub

Furthermore, neither of these folders are present on the VM:
/tmp/vagrant-chef/cookbooks-0
/tmp/vagrant-chef/cookbooks-1

If instead I ssh to the VM and run:
cd /tmp/vagrant-chef
sudo chef-solo -j dna.json -c solo.rb -r
https://s3.amazonaws.com/chef-solo/bootstrap-0.10.0.rc.0.tar.gz

I get this error:
chef 0.10.0.rc.0 error · GitHub

This is caused by either:

  1. Your cookbook_path config setting is empty
    or
  2. Your cookbook_path doesn't have a directory named cookbooks in it.
    #2 Seems designed to install the remote cookbooks into your "cookbooks"
    directory if you have both "cookbooks" and "site-cookbooks" configured in
    your cookbook_path but obviously both the implementation and the error
    messaging could be improved.

The Chef Error messaging I think was fine in this case, I think the
issue with the cookbooks-{0,1} is Vagrants - however this all ran OK
under Chef 0.9.12.
But when I get vagrant to mount the /tmp/vagrant-chef/cookbooks-* all
porceeds to the next error I reported, I'm about to check if that is
caused by the opscode/cokkbooks 0.10.rc.0 snafu discussed and fixed on
IRC earlier today.... will report back

with chef 0.10.0.rc.1 and the fixed opscode/cookbooks repo the same
error persists:

[chef] [Thu, 28 Apr 2011 04:52:33 -0700] DEBUG: Re-raising exception:
Errno::EISDIR - link[/etc/chef/webui.rb]
(chef-server::rubygems-install line 119) had an error: Is a directory

  • /etc/chef/webui.rb

Does any one have a recommended workaround?

Still failing but with some progress with the 0.10.rc.2 release and
Virtualbox 4.0.6:

$ less /var/log/chef/server-webui.log
merb : chef-server-webui : worker (port 4040) ~ Starting Thin at port 4040
merb : chef-server-webui : worker (port 4040) ~ Using Thin adapter on
host 0.0.0.0 and port 4040.
merb : chef-server-webui : worker (port 4040) ~ Successfully bound to port 4040
merb : chef-server-webui : worker (port 4040) ~ Changing privileges to chef:chef
merb : chef-server-webui : worker (port 4040) ~ Started request
handling: Sat Apr 30 01:09:06 -0700 2011
merb : chef-server-webui : worker (port 4040) ~ Params:
{"action"=>"index", "controller"=>"nodes"}
merb : chef-server-webui : worker (port 4040) ~ I cannot read
/etc/chef/webui.pem, which you told me to use to sign requests! -
(Chef::Exceptions::PrivateKeyMissing)
/usr/lib/ruby/gems/1.8/gems/chef-0.10.0.rc.2/lib/chef/rest/auth_credentials.rb:62:in
load_signing_key' /usr/lib/ruby/gems/1.8/gems/chef-0.10.0.rc.2/lib/chef/rest/auth_credentials.rb:33:in initialize'

The permissions are (600):
$ ls -la /etc/chef/webui.pem
-rw------- 1 vagrant vagrant 1679 2011-04-30 00:17 /etc/chef/webui.pem

I've tried chown chef:chef, and in case this was not a SSH style
permissions issue, I tried various chmod's to no avail.

Any suggestions?

OK the cause of this is having Vagrant mount the /etc/chef folder + this issue:

So if you have nfs installed on your Vagrant base box, you'll need to
do one of two things:

  1. remove it and vagrant will mount another less performant way -
    which is fine, since the purpose of this type of chef-server launch is
    to help devs not run in production where you should be using the
    Opscode platform :wink:
  2. Tell Vagrant not to use nfs mounting, e.g.
    csc.vm.share_folder("chef-server-etc", "/etc/chef",
    "#{@cs_kitchen}/mnt/etc", :nfs => false)

OK, so now you can launch chef-server via Vagrant.

Phew!

--
Dan DeLeo

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com

--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://wiki.hedgehogshiatus.com