-
-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uninitialized constant Extensions during Vagrant provisioning #212
Comments
+1 |
I was getting this when I was including the ES recipe in another recipe that I was actually calling. So in MY recipe, I put -- at the top -- :
And then stuff works. |
+1 |
Bernzbroad where do you put this change? I've tried to put it in the recipe where Im calling it, as well as within elasticsearch/recipes/default .. the error never goes away. What version of chef are you using? I'm stuck on 11.4 in opsworks. |
Have the same error. It seems chef solo does not require the libraries automatically. Any solutions? |
Found the solution: include "depends 'elasticsearch'" in your metafile so that elasticsearch is initialized . After that create your wrapper recipe as described. Works like a charm. |
Hello! It sounds like you were able to get this working. In the meantime, we've re-written the cookbook using libraries that expose resources and providers, so you shouldn't see this problem on the newer version. Hope this helps! |
I'm using the latest cookbook from git:
In Cheffile
My recipe:
And during provisioning, I get the following error:
This doesn't look like a configuration issue, but maybe I'm missing something?
Vagrant 1,6.2
Host: OSX 10.9.2
Guest: Ubuntu 13.10
The text was updated successfully, but these errors were encountered: