New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Small fail, with a workaround #114
Comments
Awesome information; thank you for this! I'll work on applying this to the setup task and get a fix out by EOD. |
FWIW; I don't think you missed anything; I thought I had the Chef 11.x bootstrap working solid. I had hit an issue that must of been caused by the lack of the |
It might be worth noting that the /etc/chef-server/chef-server.rb file does exist when the lab first comes up, but it looks like this:
|
Ya that's definitely missing some bits. I'm guessing this is a result of me, ineffectively, trying to force the chef-server FQDN to the IP and not the default I'll refactor the setup/bootstrap to ensure we end up using a configuration like the one you've supplied. |
Seems I'm not overriding properly; these are the current (v3.0.3) attributes passed to the Chef 11.x chef-solo bootstrap run:
|
OK I've released v3.0.4; this should be resolved now. |
w00t! It works! That's another beer I owe you ;) |
Closing this out since it's been resolved. |
Span up my first proper cc 3 test-lab. Yay!
Tried to run some tests, got this:
"This looks familiar", I thought. Ah yes, I saw this when building our new Chef 11 server. Which means I know how to fix it. So as per this (from this), I made an /etc/chef-server/chef-server.rb file, thus:
and ran
sudo chef-server-ctl reconfigure
, and now it works.Not sure if I've missed (or misunderstood) something and this is working out-the-box for other people, but whatever, I've just run my first cucumber-chef 3 test suite and I'm a VERY HAPPY SAM!
The text was updated successfully, but these errors were encountered: