[chef-testing-stack] Running unit test twice in a row fails

Bug #1395459 reported by Dr. Jens Harbott on 2014-11-23
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack + Chef
Medium
Dr. Jens Harbott

Bug Description

When running unit tests via "rake unit", the second test fails with

bundle exec berks vendor
destination already exists /Users/jrosenboom/src/cookbook-openstack-network/berks-cookbooks. Delete it and try again or use a different filepath.
rake aborted!
Command failed with status (139): [bundle exec berks vendor...]

Dr. Jens Harbott (j-harbott) wrote :

After doing a bit of searching, there is a patch in upstream berkshelf already, which will fix this issue:

https://github.com/berkshelf/berkshelf/commit/75525092a20a3194795577e1e277299d90f0a056

This will cause "berks vendor" to sync an existing cookbook directory instead of insisting to install into an empty directory.

Changed in openstack-chef:
assignee: nobody → Dr. Jens Rosenboom (j-rosenboom-j)
Dr. Jens Harbott (j-harbott) wrote :

Updating the berkshelf gem from 3.1.5 to 3.2.1 fixes the original issue, but there is still some remaining smaller issue with read-only files, handled in https://github.com/berkshelf/berkshelf/pull/1342. So I think we should wait for that latter pull request making it into a released version before updating all our cookbooks.

JJ Asghar (d-jj) on 2014-11-24
Changed in openstack-chef:
status: New → Triaged
importance: Undecided → Medium
summary: - Running unit test twice in a row fails
+ [chef-testing-stack] Running unit test twice in a row fails
Changed in openstack-chef:
milestone: none → juno-rc1
JJ Asghar (d-jj) on 2015-01-14
Changed in openstack-chef:
milestone: juno-rc1 → kilo-rc1
Mark Vanderwiel (vanderwl) wrote :

This is fixed by using the new testing repo which requires ChefDK 0.4.0 which contains berks 3.2.3. Also, the bookstrap and rakefile in each cookbook will also setup this ChefDK environment.

Changed in openstack-chef:
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers