Closed jaypipes closed 11 years ago
@jaypipes I did a bunch of hacking and it looks like I had a commit still local that should fix the missing file issue. If you update and it's still an issue, let me know. Apologies, I'm looking to get a new version cut in the next day or two and pushed up a lot of changes over the last few days.
For the path issue, it shouldn't be a huge deal as vagabond just wants a unique path on the host to store things. However, I would like it to be consistent with the cookbook name so I'll have a look and get it cleaned up.
Thanks!
No worries at all, Chris
If this is still an issue, please reopen.
Thanks!
Hi Chris,
Code that changed after the fdcb7377d7bcd3c07ead91a27eb09b364a8f8555 commit in the develop branch has caused vagabond init and vagabond status to fail, with an odd error:
After pinning my Gemfile vagabond reference to fdcb7377d7bcd3c07ead91a27eb09b364a8f8555, things started working again:
Since the error message indicates something with a
/tmp/vagabond/solos
path:you may want to look at any code that modified the Chef solo setups (though not that I don't actually use Chef solo).
Also note that the
/tmp/vagabond/solos/home/jpipes/repos/att/cloud/cookbook/infra/db/.vagabond/cookbooks/vagabond/attributes/default.rb
path has broken our infra-db cookbook into an /cookbook/infra/db path... which I'm sure is faulty.Thanks! -jay