Issue #3357 has been updated by micah -.
If facter cannot figure out the fqdn, wouldn't it be better to have it set as 'nil', rather than set it to something other than what it is? In otherwords, don't we want facter representing the real state of the system, not making things up? If there is no fqdn for the host configured, it probably should be represented as no fqdn configured for the system. Afterall, what if you wanted to find all the systems that had no fqdn set, and fix them. You would only be able to do that if the fqdn was set to 'nil' ---------------------------------------- Bug #3357: fact fqdn doesn't get set if domain fact isn't set http://projects.puppetlabs.com/issues/3357 Author: Simon Hürlimann Status: Needs design decision Priority: Normal Assigned to: Paul Nasrat Category: library Target version: 1.6.0 Keywords: domain, fqdn Branch: If the domain fact doesn't get a value (see #3356) the fqdn isn't set either. But it should probably be just the hostname in this case. Think may break in very interesting ways when using fqdn in your pupper recipes, but it won't be set. See https://bugs.launchpad.net/bugs/534773 as an example;-) -- 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://projects.puppetlabs.com/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.
