Berkshelf issue, help please


#1

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message: “Cannot
find cookbook X on any default places”

thanks


#2

On Thu, Oct 17, 2013 at 3:40 PM, Jasna Benčić jasna.bencic@teamsnap.com wrote:

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message: “Cannot
find cookbook X on any default places”

thanks

After you do berks install (which downloads and installs the
cookbooks in ~/.berkshelf/cookbooks) you need to do berks upload (or
berks up for short) to upload the new cookbook(s) to your chef
server. Once you do this, run vagrant up again, and it should find
the new/updated cookbook(s) on the server.


http://philcryer.com


#3

I did that and it didn’t work :frowning:

upload went well but got the same error after vagrant up

On Thu, Oct 17, 2013 at 10:46 PM, Phil Cryer phil@philcryer.com wrote:

On Thu, Oct 17, 2013 at 3:40 PM, Jasna Benčić jasna.bencic@teamsnap.com
wrote:

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do
berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message: “Cannot
find cookbook X on any default places”

thanks

After you do berks install (which downloads and installs the
cookbooks in ~/.berkshelf/cookbooks) you need to do berks upload (or
berks up for short) to upload the new cookbook(s) to your chef
server. Once you do this, run vagrant up again, and it should find
the new/updated cookbook(s) on the server.


http://philcryer.com


#4

Are you running chef_solo or chef_client as your provisioner in Vagrant? Do
you have the vagrant-berkshelf plugin installed?

On Thu, Oct 17, 2013 at 4:08 PM, Jasna Benčić jasna.bencic@teamsnap.comwrote:

I did that and it didn’t work :frowning:

upload went well but got the same error after vagrant up

On Thu, Oct 17, 2013 at 10:46 PM, Phil Cryer phil@philcryer.com wrote:

On Thu, Oct 17, 2013 at 3:40 PM, Jasna Benčić jasna.bencic@teamsnap.com
wrote:

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do
berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so
berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message: “Cannot
find cookbook X on any default places”

thanks

After you do berks install (which downloads and installs the
cookbooks in ~/.berkshelf/cookbooks) you need to do berks upload (or
berks up for short) to upload the new cookbook(s) to your chef
server. Once you do this, run vagrant up again, and it should find
the new/updated cookbook(s) on the server.


http://philcryer.com


#5

chef-solo, yes I have vagrant-berkshelf plugin installed

On Thu, Oct 17, 2013 at 11:22 PM, Nic Grayson nic.grayson@banno.com wrote:

Are you running chef_solo or chef_client as your provisioner in Vagrant?
Do you have the vagrant-berkshelf plugin installed?

On Thu, Oct 17, 2013 at 4:08 PM, Jasna Benčić jasna.bencic@teamsnap.comwrote:

I did that and it didn’t work :frowning:

upload went well but got the same error after vagrant up

On Thu, Oct 17, 2013 at 10:46 PM, Phil Cryer phil@philcryer.com wrote:

On Thu, Oct 17, 2013 at 3:40 PM, Jasna Benčić jasna.bencic@teamsnap.com
wrote:

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do
berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so
berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message:
“Cannot
find cookbook X on any default places”

thanks

After you do berks install (which downloads and installs the
cookbooks in ~/.berkshelf/cookbooks) you need to do berks upload (or
berks up for short) to upload the new cookbook(s) to your chef
server. Once you do this, run vagrant up again, and it should find
the new/updated cookbook(s) on the server.


http://philcryer.com


#6

Can you gist your berksfile and vagrantfile?

On Thu, Oct 17, 2013 at 4:23 PM, Jasna Benčić jasna.bencic@teamsnap.comwrote:

chef-solo, yes I have vagrant-berkshelf plugin installed

On Thu, Oct 17, 2013 at 11:22 PM, Nic Grayson nic.grayson@banno.comwrote:

Are you running chef_solo or chef_client as your provisioner in Vagrant?
Do you have the vagrant-berkshelf plugin installed?

On Thu, Oct 17, 2013 at 4:08 PM, Jasna Benčić jasna.bencic@teamsnap.comwrote:

I did that and it didn’t work :frowning:

upload went well but got the same error after vagrant up

On Thu, Oct 17, 2013 at 10:46 PM, Phil Cryer phil@philcryer.com wrote:

On Thu, Oct 17, 2013 at 3:40 PM, Jasna Benčić <
jasna.bencic@teamsnap.com> wrote:

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do
berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so
berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message:
“Cannot
find cookbook X on any default places”

thanks

After you do berks install (which downloads and installs the
cookbooks in ~/.berkshelf/cookbooks) you need to do berks upload (or
berks up for short) to upload the new cookbook(s) to your chef
server. Once you do this, run vagrant up again, and it should find
the new/updated cookbook(s) on the server.


http://philcryer.com


#7

here is gem list of berkshelf

*** LOCAL GEMS ***

berkshelf (2.0.10, 1.3.1)

for Vagrantfile and Berksfile I get nothing, empty

On Thu, Oct 17, 2013 at 11:26 PM, Nic Grayson nic.grayson@banno.com wrote:

Can you gist your berksfile and vagrantfile?

On Thu, Oct 17, 2013 at 4:23 PM, Jasna Benčić jasna.bencic@teamsnap.comwrote:

chef-solo, yes I have vagrant-berkshelf plugin installed

On Thu, Oct 17, 2013 at 11:22 PM, Nic Grayson nic.grayson@banno.comwrote:

Are you running chef_solo or chef_client as your provisioner in Vagrant?
Do you have the vagrant-berkshelf plugin installed?

On Thu, Oct 17, 2013 at 4:08 PM, Jasna Benčić <jasna.bencic@teamsnap.com

wrote:

I did that and it didn’t work :frowning:

upload went well but got the same error after vagrant up

On Thu, Oct 17, 2013 at 10:46 PM, Phil Cryer phil@philcryer.comwrote:

On Thu, Oct 17, 2013 at 3:40 PM, Jasna Benčić <
jasna.bencic@teamsnap.com> wrote:

Ohai

Got one problem with Berkshelf…

Ok, I have cookbook X which depends on several other cookbooks. I do
berks
install under that cookbook and everything great.

I do vagrant up under that cookbook and it fails at recognizing one
dependency cookbooks which was successfully installed and placed
under
.berkshelf/cookbooks

Is there something else that should be set under Vagrantfile so
berkshelf
doesn’t fail during vagrant up? I mean that I don’t get message:
“Cannot
find cookbook X on any default places”

thanks

After you do berks install (which downloads and installs the
cookbooks in ~/.berkshelf/cookbooks) you need to do berks upload (or
berks up for short) to upload the new cookbook(s) to your chef
server. Once you do this, run vagrant up again, and it should find
the new/updated cookbook(s) on the server.


http://philcryer.com