Skip to content
This repository has been archived by the owner on Dec 26, 2017. It is now read-only.

vagrant-berkshelf not vendoring cookbooks to correct location #291

Open
jat850 opened this issue Aug 22, 2015 · 0 comments
Open

vagrant-berkshelf not vendoring cookbooks to correct location #291

jat850 opened this issue Aug 22, 2015 · 0 comments

Comments

@jat850
Copy link

jat850 commented Aug 22, 2015

I'm using vagrant-openstack-provider and during its use, while trying to execute the provision step, I have discovered that my home directory's .berkshelf/vagrant-berkshelf/shelves/md5hashed_directory/cookbooks is not populating at all. This means that when the vagrant provision step attempts to run my chef-solo provisioning, it finds no cookbooks at the rsync step.

I'm using:

  • vagrant-berkshelf 4.0.4
  • berks 3.2.4
  • vagrant 1.7.4

I run: vagrant up --provider=openstack

Partial log:

Bringing machine 'coreapi' up with 'openstack' provider...
coreapi: The Berkshelf shelf is at "/home/username/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150822-26011-eqgf2v-coreapi"

After the provision fails (Cookbook X not found), I did this:

ls ~/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150822-26011-eqgf2v-coreapi/

And there are no files found. vagrant-berkshelf does not appear to be running the "Vendor" step whereas when using virtualbox as the provider, it does, and it populates the vagrant-berkshelf shelf as expected.

When running with virtualbox as the provider, there is clear logging at the vendoring step as the cookbooks copy to the vagrant-berkshelf shelf; no such output at all occurs when using the openstack provider.

I have "config.berkshelf.enabled = true" in my Vagrantfile.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant