This repository has been archived by the owner on Jul 14, 2021. It is now read-only.
kitchen-vagrant errors #378
Comments
|
Related to test-kitchen/kitchen-vagrant#165 ? |
|
@jdmundrawala I don't think so, the systems which are included in the default .kitchen.yml file are ubuntu-12.04 and centos-6.5. |
fnichol
added a commit
to test-kitchen/kitchen-vagrant
that referenced
this issue
May 7, 2015
This update attempts to improve on a2ef401 which remains a workaround until the work of continuously publishing Bento boxes to Atlas is completed. The rationale and rules in the above mentioned commit remain, but now only the platform name is checked. In other words, if the platform name begins with one of the following (case-sensitive): * `centos` * `debian` * `fedora` * `freebsd` * `opensuse` * `ubuntu` then the platform is assumed to have a Bento box, hosted in the pre-determined S3 bucket. References #165 References test-kitchen/test-kitchen#707 References test-kitchen/test-kitchen#663 References chef-boneyard/chef-dk#382 References chef-boneyard/chef-dk#378
fnichol
added a commit
to test-kitchen/test-kitchen
that referenced
this issue
May 7, 2015
The updated platforms are: - ubuntu-14.04 - centos-7.1 References #707 References #663 References chef-boneyard/chef-dk#382 References chef-boneyard/chef-dk#378
fnichol
added a commit
to test-kitchen/test-kitchen
that referenced
this issue
May 7, 2015
The updated platforms are: - ubuntu-14.04 - centos-7.1 References #707 References #663 References chef-boneyard/chef-dk#382 References chef-boneyard/chef-dk#378
|
I think this is fixed by upgrading Kitchen Vagrant, which will be released in ChefDK 0.6 (expected to ship later today). Let me know if upgrading doesn't fix. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On a new install of ChefDK 0.4.0 on CentOS 6.6 running
kitchen listimmediately afterchef generate cookbook testbookresults in errors about the vagrant driver not being able to be loaded.In #15 it was suggested that removing kitchen-vagrant 0.17.0 would solve the problem, and it did in this case.
I'm not really sure what the root-cause of this issue is, but it's quite inconvenient to need to remove something packaged with chef to make this work.
The text was updated successfully, but these errors were encountered: