Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
[DE65]: runit cookbook making installs fail #352
When uploading cookbooks to chef server running chef-server version 10.12.0, upload fails with the following error:
FATAL: Cookbook file test/spec/libraries/provider_runit_service_spec.rb has a ruby syntax error:
Adding '' characters onto the end of lines before problem lines passes the syntax check so upload succeeds.
I'm getting the same traceback with chef-server 11.0.2 with embedded ruby 1.9.3, no other ruby in the path, and knife 11.2.0 on the client.
root@infra01:~# ssh email@example.com 'which ruby ; echo $?'
root@infra01:~# ssh firstname.lastname@example.org '/opt/chef-server/embedded/bin/ruby -v'
root@infra01:~# knife -v
root@infra01:~# knife client list -VV
@JCallicoat Are you sure that you're using chef server 11? This is a known problem only with chef server 10 since the runit cookbook is using ruby 1.9 syntax, which ruby 1.8.7 doesn't like.
Either way, the runit cookbook was actually fixed to remove this syntax (https://github.com/opscode-cookbooks/runit/pull/28/files) and we have updated the submodule pointer to point to this commit in the latest version of the cookbooks. So, in the product, this has been fixed, though not necessarily packaged yet (nor yet pushed into the master branch of the chef-cookbooks repo). For the versions of the cookbooks you're using, you'll be able to get around this by manually updating to the latest version of the runit cookbook:
As I said, this will fix the issue, which is only an issue if you're using chef server 10
I totally understand that the ruby bundled with the chef version I'm using should handle the syntax; that's why I listed the bundled ruby version and made sure there were no other rubys in my path. I understand the runit cookbook is maintained upstream, and merging the ruby 1.8.7 patchset is good (though I swear I'm on erchef 11 / ruby 1.9.3 :P). I commented on this bug because I ran into this even though it seems like I shouldn't have. Will try to reproduce and include details.