| popularity | question | answers | views | user | |
|---|---|---|---|---|---|
| 2 |
Abandoned cookbooks
There seem to be cookbooks that have been uploaded at one point in time, and have never been updated, nor respond to any inquiries regarding updates. I have taken on primary maintenance of one such cookbook, have updated it considerably, and would like to share it back. Is there a method or process to determine ‘ownership’ of a given cookbook, and delegate that to another interested party if it is neglected? Thanks, -M |
0 | 341 | ||
| 2 |
Overriding attributes referenced by other attributes
I am having trouble understanding the proper way to define my recipe’s attributes and allow for certain ones to be overridden in roles. The classic example is where you have one attribute for the version of an external library and then another attribute that constructs a URL which references the first version attribute. Then, if the version number is overridden, the URL gets updated as well. Example: attributes/default.rb
recipes/default.rb
roles/noodle.rb
chef-client run output
Using ‘override_attributes’ instead of ‘default_attributes’ doesn’t make a difference:
chef-client run output
I have discovered that if I literally set one of those attributes on the node, it gets picked up. Set node attribute with ‘knife node edit NODE’:
Then a chef-client run shows:
Isn’t this what roles are for? I need to be able to manage attributes like this en masse and in source control (role files). There are several official cookbooks that are designed the same way such as java, couchdb, and munin so it seems like it should be supported somehow. |
1 | 1.3k | ||
| 1 |
Opensource Chef 11 server behind a firewall
Hi, I just upgraded our old Chef server to Chef 11, But I’m struggling to get my clients to reach the server. Our Chef-server is hosted internally, while our clients are in the cloud. Between them there’s a firewall that blocks all connections from the internet to the internal network. Since Chef-client now connects to port 80 or 443, I’m unable to setup a portforward to Chef-client to work without exposing the Chef Webinterface. Is there a way to tell Chef to use other ports for all communication? I tried setting the following in chef-server.rb. But this works only halve, the clients are added to the node-list, but the cookbook transfer fails because it wants to connect to https://chef-server.tld/bookshelf/organization….
Any ideas? |
0 | 12 | ||
| 1 |
Mount a network drive to windows using Chef-solo
I need to mount a network drive on a windows vm. I am currently using chef solo to automate the process. This is what I have in my recipe file:
This does not work and I get the following error messages:
I can manually map the drive on the windows vm, but then I need to provide a domain-name-qualified user name and password. Is there a way I can provide the domain name, user name, password to the mount resource? is there an alternate way to mount the drive using chef? I also tried the following command (as suggested in http://docs.opscode.com/ctl_chef_client.html)
After I entered password, a window appears and then dissapears. So I don’t exactly know what is happenning in it. I am an absolute new by to chef, so a detailed answer would be very much appreciated. Thanks. |
2 | 48 | ||
| 1 |
Bootstrapping
Hi Can anyone help? Thanks |
1 | 83 | ||
| 1 |
knife command not working
hi , Knife command throwing error below . /usr/bin/knife:22:in `require': no such file to load — chef/application/knife (LoadError)
How to solve this ? |
0 | 72 | ||
| 1 |
In chef-solo, creating data bags or users within recipe generates FATAL: Net::HTTPServerException: 403 "Forbidden"
Whenever I execute chef-solo, I get this error [2013-03-05T20:59:50+09:00] INFO: Chef 10.18.2 [2013-03-05T20:59:51+09:00] INFO: Setting the run_list to “role[test_ruby]” from JSON [2013-03-05T20:59:51+09:00] INFO: Run List is [role[test_ruby]] [2013-03-05T20:59:51+09:00] INFO: Run List expands to [ADMINS] [2013-03-05T20:59:51+09:00] INFO: Starting Chef Run for sg8tb08208 [2013-03-05T20:59:51+09:00] INFO: Running start handlers [2013-03-05T20:59:51+09:00] INFO: Start handlers complete. [2013-03-05T20:59:51+09:00] INFO: HTTP Request Returned 404 Not Found: Action ‘update’ was not found in DataBags [2013-03-05T20:59:51+09:00] INFO: HTTP Request Returned 403 Forbidden: You are not allowed to take this action. Recipe Compile Error in /var/chef-solo/cookbooks/ADMINS/recipes/default.rb Net::HTTPServerException 403 “Forbidden” Cookbook Trace: /var/chef-solo/cookbooks/ADMINS/recipes/default.rb:12:in `from_file' Relevant File Content: /var/chef-solo/cookbooks/ADMINS/recipes/default.rb: 5: # Copyright 2013, YOUR_COMPANY_NAME 6: # 7: # All rights reserved – Do Not Redistribute 8: # 9: 10: users = Chef::DataBag.new 11: users.name(“users”) 12>> users.save 13: 14: puts “[INFO] Finished!” 15: [2013-03-05T20:59:51+09:00] ERROR: Running exception handlers [2013-03-05T20:59:51+09:00] ERROR: Exception handlers complete [2013-03-05T20:59:51+09:00] FATAL: Stacktrace dumped to /var/chef-solo/chef-stacktrace.out [2013-03-05T20:59:51+09:00] FATAL: Net::HTTPServerException: 403 “Forbidden” Below is the procedure I did, In Chef workstation,
~/chef.json contents are: { “run_list”: “role[test_ruby]” }I have re-registering the node again, restarting solr, couchdb, rabbitmq and server but the error persists. If not, the error changes to Error 401 “Unauthorized” UPDATE: ADMINS is a self-made cookbook. |
1 | 125 | ||
| 1 |
Chef Server 11 high memory usage
I just tried installing a Chef master server on an Amazon EC2 micro instance. After crashing it a couple of times I was only able to get it working using a lot of swap. The server easily eats away 600mb of ram without anything connected to it. This can not really be normal behaviour? Is this a bug in the latest version? Can I disable features of Chef that I am not using (indexer, webui) to lower this? |
0 | 66 | ||
| 1 |
Chef API and Ohai
Is it possibly to query a node’s system information gathered by Ohai using the Chef API? |
1 | 76 | ||
| 1 |
getaddrinfo: nodename nor servname provided, or not known (SocketError)
I am following the getting started steps on the wiki to set up a chef server, workstation and a node. I managed to get all 3 of them working, I can see the master server’s webui, I can run ‘knife client list’ on my workstation and my node is in that list. I then installed the ‘chef-client’ cookbook and tried to upload it to the master server with
I am running both server and node as a virtual machine for development purposes. The master server is configured in the knife.rb file as Does anyone know what is causing this problem? |
3 | 687 |
