[chef] Re: Re: setting the fqdn

[Sam Darwin < >]

create a new EC2 instance manually:  ip-10-60-6-141.ec2.internal

then run this command:

knife bootstrap 10-60-6-141 -r 'recipe[fqdn]' -N node123.example.com

looking on the node itself, everything is correct.   the name is now
node123.example.com

looking on chef-server, the fqdn of the new instance is
ip-10-60-6-141.ec2.internal , which is what it saw when it first
connected to this new machine.



On Wed, Jun 12, 2013 at 7:00 PM, Sean OMeara 
<
 >
 wrote:
> Are you bootstapping with -N
>
> knife bootstrap 1.2.3.4 -r 'recipe[superserver]' -N node123.example.com
>
> -s
>
>
> On Wed, Jun 12, 2013 at 11:54 AM, Sam Darwin 
> <
 >
> wrote:
>>
>> Hi Sean,
>>
>> 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 
>> <
 >
>>  wrote:
>> > check out the fqdn cookbook to set this on linux
>> >
>> >
>> > On Tue, Jun 11, 2013 at 8:39 AM, Sam Darwin 
>> > <
 >
>> > wrote:
>> >>
>> >>
>> >> FQDN originates from the hostname in some way.   If the hostname is
>> >> being
>> >> set
>> >> on the first chef run through a recipe, it appears you have to run
>> >> chef-client
>> >> 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.
>> >
>> >
>
>