You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 26, 2017. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
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.
The text was updated successfully, but these errors were encountered: