epel recipe in http://s3.amazonaws.com/chef-solo/bootstrap-latest.tar.gz has pointed to an old ( not exist anymore ) epel rpm.

I run into the same issue. Unfortunately, changing it then running the command to install chef-server doesn't work because it reverts back.
CentOS 6.2 64bit

Error yum::epel line 26

also adding the proper Epel repo does not resolve this issue.

Thanks to the original poster and Thanks in advance for the added support toward resolving this issue.

Hi! thing I have exactly the same problem like Daniel. I edit the
chef-solo/cookbooks/yum/attributes/default.rb
and running
sudo chef-solo -c /etc/chef/solo.rb -j ~/chef.json -r https://s3.amazonaws.com/chef-solo/bootstrap-latest.tar.gz
this ends up with the following error:
FATAL: Net::HTTPServerException: remote_file[/tmp/chef-solo/epel-release-6-5.noarch.rpm] (yum::epel line 26) had an error: Net::HTTPServerException: 404 "Not Found"
and the /yum/attributes/default.rb has the old "6-5" setting again

Anyone has another workaround maybe?

Thanks in advance,
Alex

found a workaround myself, just to let you know...

first run
sudo chef-solo -c /etc/chef/solo.rb -j ~/chef.json -r https://s3.amazonaws.com/chef-solo/bootstrap-latest.tar.gz
this will break with the 404 "not found" error, but before that it will extract all files to the path you specified in the solo.rb file

edit the cookbook/yum/attributes/default.rb from as suggested in the original post and then re-run
sudo chef-solo -c /etc/chef/solo.rb -j ~/chef.json

regards,
Alex

Can someone try with:

sudo chef-solo -c /etc/chef/solo.rb -j ~/chef.json -r https://s3.amazonaws.com/chef-solo/bootstrap-unreleased.tar.gz

Cheers.

Also, you can also set the yum attribute (or any others) in the JSON file:

{
  "chef_server": {
    "server_url": "http://localhost:4000"
  },
  "yum": {
    "epel_release": "6-7"
  },
  "run_list": [ "recipe[chef-server::rubygems-install]" ]
}

I want to thank Alex Linke for the workaround because that really helped me get Chef-server into the kitchen.

Also, thanks to Joshua Tiberman for replying with this fix and the code to set the yum attribute. I have tested it and the script completes successfully.

However, I was wondering if there is any difference in the installs other than the method used to complete it. Is it possible that because the workaround didn't require the bootstrap url that there may be some dependencies or other things that may be missing?

I'm going to close this issue as fixed because the yum cookbook will use 6-7 as the EPEL version now, and the bootstrap tarball will be updated soon; in the interim use the attribute change described above in JSON if you need to set up a Chef Server.