-
Notifications
You must be signed in to change notification settings - Fork 24
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
FATAL: NameError: uninitialized constant Chef::Recipe::Opscode #10
Comments
Adding
|
Honestly, I'm not sure what the Chef-y way to do this is. Since the cookbook declares OpenSSL as a dependency, I'm inclined to have our cookbook simply do what's required without human intervention. I wonder if it would be enough to add |
I can try that! Let you know if it works. |
Any update on the best fix to this? - adding openssl to the runlist seems a bit nasty. Adding include_recipe "openssl" doesn't seem to work - presumably because the default recipe is empty and the needed code is in a library. |
Sorry this got buried. I believe adding openssl worked. |
Is there a way to include openssl from the postgresql cookbook/recipe? - adding: include_recipe "openssl" doesn't work. Adding it to the runlist works, but I don't really want that cluttered. Thanks, Ian |
Hmm yeah I don't know how else. Yes, you're right it'll get cluttered though. |
Using both:
And adding dependency to my site-cookbook like this:
... solved my problem without cluttering the runlist. |
Usually you don't need to include_recipe a library cookbook. To access the methods it should work to depend it in the metadata.rb:
|
I'm running into an error
FATAL: NameError: uninitialized constant Chef::Recipe::Opscode
when I attempt to run the server recipe.I'm on Ubuntu 10.04.
It seems that others have run into it too.
Perhaps there's something wrong with the way we configured stuff?
You can see the full error here.
The text was updated successfully, but these errors were encountered: