andrewhavens
commented
10 years ago I'm not sure that the error has anything to do with vagrant-chef-zero. What does your Vagrantfile look like?
Open jpic opened 10 years ago
andrewhavens
commented
10 years ago I'm not sure that the error has anything to do with vagrant-chef-zero. What does your Vagrantfile look like?
andrewhavens
commented
10 years ago Ooh, I just came across a comment in vagrant-berkshelf issue #186 that leads me to believe this is an issue with vagrant-berkshelf
andrewhavens
commented
10 years ago Here's another issue which specifically mentions the same error you're seeing: berkshelf/vagrant-berkshelf#188. Looks like it's due to a bad monkey patch, but it's not vagrant-chef-zero's fault.
andrewgross
commented
10 years ago Thanks for reporting this and following up. While I don't require i18n I think one of the dependencies does. Unfortunately, chef-api isn't ready to replace ridley at this time, which I believe would fix the issue.
bmurtagh
commented
10 years ago I have a similar issue that I posted as #55, but I'm not using Berkshelf so I'm unsure how to address the issue. I don't know if upgrading to the newest Vagrant would help, but I've held off for now until some brighter minds can hopefully provide some better advice.
andrewgross
commented
10 years ago I haven't gotten this working on 1.6.x yet, only up through 1.5. Will investigate soon.
jjasghar
commented
9 years ago I attempted with Vagrant 1.6.3 and no dice. Down grading to Vagrant 1.5.4 didn't work either.
vagrant-berkshelf (2.0.1)
vagrant-chef-zero (0.7.1)
vagrant-login (1.0.1, system)
vagrant-omnibus (1.4.1)
vagrant-share (1.1.0, system)
colby
commented
9 years ago Just got bit by this issue too.
johntdyer
commented
9 years ago Anyone get past this yet?
jjasghar
commented
9 years ago Honestly, i just converted to https://github.com/opscode/chef-metal. It leverages the same stuff, but wraps it up all in a fun little package.
cyberflow
commented
9 years ago +1 Need solution.
YpNo
commented
9 years ago +1 with vagrant 1.6.3, vagrant-chef-zero 0.7.1 I don't use berkself
willejs
commented
9 years ago +1
ghost
commented
9 years ago I was able to get past something similar by installing my vagrant plugins in specific order.
Vagrant 1.6.3 vagrant-berkshelf 2.0.1
vagrant-chefconfig
vagrant-omnibus
Someone might want to get the plugin install order a shot?
brettcave
commented
9 years ago This issue is that the i18n slice function crashes if a filter key is not found in the source hash. Ridley expects the slice function to work safely like this, assuming that all keys passed to the slice function are in the original hash.
A workaround is to modify the i18n slice function to not require all filter keys in the hash
def slice(*keep_keys)
h = {}
keep_keys.each { |key|
h[key] = fetch(key) if has_key?(key)
}
h
end unless Hash.method_defined?(:slice)(I've added if has_key?(key) test while building up the new hash.
I've opened an issue on the i18n project and created a PR to resolve this: https://github.com/svenfuchs/i18n/pull/292
colby
commented
9 years ago Thanks @brettcave, I can confirm that manually patching it works.
Do we need to lean on the maintainers of that gem to pull in that PR? It looks like there's a decent backlog of PRs already submitted.
Couldn't get the repo to vagrant up: