Are you using the “-N” option with your knife bootstrap command? That sets the node name in the Chef server. I image something like this would work:
knife bootstrap mynode -N mynode.mydomain.com
From: Sam Darwin [mailto:email@example.com]
Sent: Wednesday, June 12, 2013 08:55
To: Sean OMeara
Subject: [chef] Re: Re: setting the fqdn
I just tried out the fqdn cookbook. It appears to not solve the
problem I was mentioning which is that two runs of chef-client are
required. that is still the case. I would like the fqdn to be
correct in the chef server so that nagios can use it. the first run
of the fqdn recipe will fix the name on the client itself, but not on the chef server, and so a second run of chef-client is required.
this is relevant because we are commonly bootstrapping new clients with “knife ec2 server create” and “knife bootstrap” , and these usually run chef-client a single time, not twice, and then nagios
picks up the new server name. But nagios is not getting the right
fqdn , even with the fqdn recipe being part of the bootstrap.
On Tue, Jun 11, 2013 at 4:01 PM, Sean OMeara firstname.lastname@example.org wrote:
check out the fqdn cookbook to set this on linux
On Tue, Jun 11, 2013 at 8:39 AM, Sam Darwin
FQDN originates from the hostname in some way. If the hostname is being
on the first chef run through a recipe, it appears you have to run
twice to get the FQDN into the chef server. sound right?
The first run of chef-client will pick up the original (and wrong)
fqdn, and input that into chef server.
The second chef-client run will get the new, and correct, fqdn.