Can I set fqdn for chef nodes?

chef-infra knife
nroose picture nroose · Feb 11, 2013 · Viewed 16.1k times · Source

I have several servers set up with a custom internal local domain - x.local. So I have servers s1.x.local, etc. My knife reports the fqdn as s1.domain.com. Can I change that without changing the names the servers think they have? Or do I need to actually change the server names? Thanks.

Answer

Jordan Dea-Mattson picture Jordan Dea-Mattson · Feb 26, 2013

You can, but it will not stay set to the value you give it.

The FQDN attribute is what is known as an automatic attribute in Chef. It is set by Ohai each and every time Ohai runs.

Therefore, while you can change the value of the FQDN attribute, the next time Ohai runs, it will set it back to be the value returned by hostname --fqdn.

Therefore, as noted above, if you want to change the FQDN attribute permanently, you will need to change the hostname.

Related questions

Which special characters need escaping in a solr query?

Update: I think this question has to do with solr syntax in general, and not Chef in particular. So while I ran into this working with Chef, I presume that anyone working with Solr will also experience this... I'm working …

Read More
Private key could not be loaded when I run "knife client list"

Configuration file written to /home/ubuntu/sudo /home/ubuntu/chef-repo/.chef/knife.rb ubuntu@mychefclient:~$ knife client list WARNING: No knife configuration file found ERROR: Your private key could not be loaded from /etc/chef/client.pem Check your configuration …

Read More
Chef clients and validators

I'm trying to understand the concept of Chef clients and validators, and their relationship to the bootstrapping process. According to this article, the chef-client will use the /etc/chef/validation.pem private key to authenticate itself for the initial run, …

Read More