On Jun 29, 7:47 pm, Sriramu Singaram <sriramus....@gmail.com> wrote: > Hi Everyone, > > I am using Puppet 2.6.5 to configure fresh VMs. These VMs have their > hostname set to localhost.localdomain initially at boot-time. > > There is this script file that runs in rc.local and this is what I do > inside it > 1. I change the hostname from localhost to xxx.xxxxxx using the > hostname command. > 2. start the puppet agent as /usr/sbin/puppetd --certname=xxx.xxxxxx > --logdest=/var/log/puppet/puppet.log > > The problem I am facing is that the puppet agent on the VMs creates > certificates for localhost.localdomain inspite of me changing the > hostname to say xxx.xxxxxxx. > > I want the puppet agent to pick up the new hostname while creating the > certificate, but it doesn't seem to be doing that. > > I am not sure where the puppet agent looks to pick up the hostname at > certificate creation, is it the /etc/hosts file or the env or /etc/ > sysconfig/network? currently when I set the hostname using the > hostname command, it doesnt create any entry in these files. > > Any help is really appreciated!!
In all likelihood, the agent uses the node's name resolver to get its FQDN, either by a command such as 'hostname --fqdn' or by the direct syscalls. Changing the host name via the hostname command does not affect the FQDN, and also does not persist across reboots . How you can change the FQDN and whether you can do so without restarting the VM will depend on your configuration and resolver library. Among the relevant files for most Linux installations are / etc/nsswitch.conf, /etc/resolv.conf, and /etc/hosts. Other files vary more among distributions, but on RedHat-family distros you probably need to set the FQDN in /etc/sysconfig/network. Whether the node's name is in fact resolvable in DNS / NIS / whatever-nameservice-is- configured may also be relevant. If you are running a name caching service (e.g. nscd) then that may also factor into the equation. Note that nscd in particular can be configured to be stubbornly ignorant of changes to the authoritative files. Good luck, John -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
