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.
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>
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: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.
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