Issue Details (XML | Word | Printable)

Key: COOK-251
Type: Improvement Improvement
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Joshua Timberman
Reporter: Alex Soto
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Chef Cookbooks

AWS ebs_volume resource should work under chef solo

Created: 05/Feb/10 10:21 PM   Updated: 05/May/10 10:25 PM   Resolved: 08/Feb/10 08:44 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None


 Description  « Hide

Using the AWS ebs_volume resource fails under chef-solo because it invokes node.save in the create and attach actions.

I worked around it by checking the state of Chef::Config.solo.

Example here: <http://github.com/apsoto/cookbooks/commit/9ca02dec056763a719cd388695ce2cd0f9764b69>



Sort Order: Ascending order - Click to sort in descending order
Alex Soto added a comment - 18/Feb/10 09:24 AM

Any details on the fix? I don't see any changes in the cookbooks github repo.

On a somewhat similar note, this problem arose while testing under chef-solo, but once I tested under chef-client, the node.save invokes a connection attempt to the stomp server, so it seems calling node.save doesn't work in a recipe regardless.

I was told this is fixed in 0.8. I'm using .7.16. I worked around in my own fork for this as well for clients prior to 0.8
<http://github.com/apsoto/cookbooks/commit/a7c59a92997e96e3057aa6b49f856e775fe7bec4>


Joshua Timberman added a comment - 05/May/10 10:22 PM

Hi Alex!

Thanks for the fixes. I've adjusted the version check to not rely on Gems, since we might be running on a system that was installed via packages and not have RubyGems installed.


Joshua Timberman added a comment - 05/May/10 10:25 PM

Merged!