Issue #2085 has been updated by Paul Nasrat. Status changed from Accepted to Closed
Commited Ohad's patch for this may revisit how all this works later though ---------------------------------------- Bug #2085: facter determins fqdn in strange and suboptimal ways http://projects.reductivelabs.com/issues/2085 Author: Chris MacLeod Status: Closed Priority: High Assigned to: Luke Kanies Category: library Target version: 1.6.0 Keywords: Branch: In certain scenarios facter will make strange decisions in determining the value for the fqdn (and domain) fact. This can lead to misleading results. In a NIS environment when a host is under a subdomin facter will use 'domainname' to determine the domain fact and then use that to set the fqdn fact. domainname (the command) will return the configured nis domain or "(none)" if no nis domain is configured. -- Example 1 -- host in nis environment with subdomain # hostname foo.bar.example.com # domainname example.com # facter domain example.com # facter fqdn foo.example.com -- Example 2 -- non-nis environment # hostname foo.bar.example.com # domainname (none) # facter domain bar.example.com # facter fqdn foo.bar.example.com It seems that facter should use hostname if it's set (and fully qualified) to determine the fqdn rather then try to build it from pieces. Assuming hostname is only reporting short hostname then building it from domainname is in consistent. facter version: facter-1.5.2-1.el5 host os: rhel5 -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
