I’ll happily try those debug steps tonight. However, perhaps you could
explain somewhere (here or point me at an existing page) about how you
envision the use case being met in the future.
i.e. I want to take an existing cookbook, customise it a bit, but still be
able to pick up changes to the parent cookbook when they’re made and I’m
happy with them.
Concrete example for discussion purposes: I recently took the wordpress
cookbook and had to modify it and the code around it in order to attach an
EBS volume for the database, include the FeedBurner plugin and my theme,
work with Apache and Tomcat so I can send tomcat traffic to tomcat and blog
traffic to Wordpress, etc.
On Wed, Apr 27, 2011 at 10:11 PM, Daniel DeLeo email@example.com wrote:
On Friday, April 22, 2011 at 7:01 PM, Tom Thomas wrote:
On Fri, Apr 22, 2011 at 3:30 PM, Edward Sargisson firstname.lastname@example.org:
Yes I was targetting a specific Availability Zone. In order to bring my
production site back up I had to use Chef 0.9 and specify a region to bring
I’ve just tried the same command with 0.10.0.RC.0 and it still fails in
exactly the same way.
if the chef version change had an impact, then it wasn’t due to AWS issues.
I’ll leave analysis on why Chef 0.9 v. 0.10.0.RC had an impact on the
issues’ occurrence to someone more qualified than me.
For clarity, I’m running Knife on a Windows client to startup an Ubuntu
instance in the cloud. The link below indicates that WinRM is required on
the Windows servers - not the client.
So, would you still like me to try it?
ah, well then, probably not worth trying based in that sorry I wasn’t
of any help.
In general, I’d recommend you migrate away from using site-cookbooks to
stitch together modified cookbooks.
That said, to debug this issue, it’d help if you can add
pp @cookbook_settings between line 67 and 68 of
chef/cookbook/cookbook_version_loader.rb and look for anything that stands
out (you can find the file with
gem which chef/cookbook/cookbook_version_loader