Issue Navigator

Chef::Config[:solo] not being set in Solo runs

chef-solo json attributes aren't loaded

chef-client and chef-solo will fail to run ohai if the node_name is explicitly configured.

chef-solo tries to get templates from localhost:4000

Attributes added from an attribute file can unneccessarily block run list expansion

Chef is too 1337 4 u

Remote File tests failing after Solo updates

Chef Solo does not obey the file selection laws

CookbookLoader#load_cascading_files uses Dir.glob(array) syntax, which is unavailable on RHEL and Centos

delayed notifications should coalesce so they don't run multiple times

git resource fails on subsequent checkouts of the same repostiry

Provider detection broken if Resource type and Provider name matches

chef-solo fails to download remote recipes because application/solo.rb no longer uses open-uri

NoMethodError running chef-solo

callback scripts in deploy/ directory of deployed application repository no longer get run

Chef::ShellOut::Windows is exhibiting multiple issues in 0.10.6

"can't convert nil to String" error in `link` resource

Post-run cookbook cleanup is getting triggered on chef-solo, deleting files from cookbooks

chef cookbook_file fails on OSX when using a (valid) group name including a space

Chef cookbook_file fails on OSX when assigning file to an owner with a large numeric userID

Chef Server installation via Bootstrap didn't work in 11.0.0

CHEF-1202 filenames with brackets, filenames regular expression escape

chef-solo needs /etc/chef to exist

Nested hashes loaded from JSON don't act like nested hashes

Ruby 1.9 Support for Chef

All service providers ignore ignore_failure attribute

Inconsistent attributes

chef-solo does not always set Chef::Config[:solo] to true, Chef::Application::Solo should require 'chef'

Require chef loads everything

Chef will block forever reading IO, even on processes that don't play nicely with their filehandles

SCM providers do not set resource updated (notifications)

Chef::Node::Attribute can't handle false/nil

Wrong Permission are Set

deploy_revision doesn't find provided revision tag

hey yo

Add --noop support

2nd try: Delayed scripts don't run on failure

Chef::Node does not properly validate the name parameter

Role error messages are non-helpful to track down which role caused the problem (when loading roles from filesystem)

Chef::Node parameter validation is not strict enough (in particular the name attribute)

Running the features should not require sudo (mac-dev-start)

Metadata Fail on files and custom paths

chef-solo needs to be run 3 times to succeed on ubuntu 10.4

Update regular expression placeholders to quote substituted values.

LWRP should output to the log when overriding and existing resource or provider

Add ability to persist/lookup Resources to/from node

Installation of chef-server gem via chef-solo fails on a clean machine

Role support

chef-solo fails to execute recipes on localized systems