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

Reconfigure doesn't handle not having a hostname set well #21

Open
jmink opened this Issue Nov 11, 2014 · 3 comments

Comments

Projects
None yet
4 participants
@jmink
Contributor

jmink commented Nov 11, 2014

Behavior:
A chef-server-ctl reconfigure dies with the error: FATAL: RuntimeError: Please add a server section for to /etc/opscode/private-chef.rb!

This appears to be due to the server not having a valid hostname set, therefore cookbooks/private-chef/recipes/default.rb:87 indexes into the config with nil or "" and doesn't find the local host and complain. It would be cleaner to just error if the host name is 0 characters.

@jmink jmink added the enhancement label Nov 11, 2014

@markan markan added this to the accepted-minor milestone May 13, 2015

@irvingpop

This comment has been minimized.

Contributor

irvingpop commented May 13, 2015

This is one of the most common first issues encountered by new Chef server users. We do state in the documentation that A resolvable hostname that is specified using a FQDN or an IP address but we could make it more intuitive

@sdelano

This comment has been minimized.

Contributor

sdelano commented May 13, 2015

A good user experience here would be something along the lines of:

Chef Server could not resolve your hostname: (p.s. it's blank)

Please set it with ...

in HA mode, we could even go one step further to note that you should also have an entry in chef-server.rb for each server that corresponds to that hostname.

@irvingpop

This comment has been minimized.

Contributor

irvingpop commented May 13, 2015

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment