Jira (FACT-168) Changed domain and fqdn facts

[David LeVene (JIRA)]

Title: Message Title

David LeVene commented on an issue   Re: Changed domain and fqdn facts Thought I'd add my comments to this - as I'm having the same issue. A lot of our fleet is still running facter 1.6.18 due to this. We only see this on our hosts which have IPv6 Enabled only - so this output below is from a host that does not have an IPv4 Address. Hosts which have both v4 & v6 resolve correctly. We are running RH 6.4 at the moment hostname -f hostname: No address associated with name hostname vmhost-prod-1.loc.example.com.au dnsdomainname dnsdomainname: No address associated with name facter-1.6.18-1.el6.x86_64 facter -p hostname fqdn domain domain => loc.example.com.au fqdn => vmhost-prod-1.loc.example.com.au hostname => vmhost-prod-1 facter-2.2.0-1.el6.x86_64 facter -p hostname fqdn domain domain => example.com.au fqdn => vmhost-prod-1.example.com.au hostname => vmhost-prod-1 cat /etc/resolv.conf domain example.com.au search example.com.au cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 IPV6 ADDRESS vmhost-prod-1.loc.example.com.au vmhost-prod-1 Note, if I add the following into /etc/hosts 127.0.1.1 vmhost-prod-1.loc.example.com.au I get these results from facter-2.2.0-1.el6.x86_64 hostname -f vmhost-prod-1.loc.example.com.au hostname vmhost-prod-1.loc.example.com.au dnsdomainname loc.example.com.au facter -p hostname fqdn domain domain => loc.example.com.au fqdn => vmhost-prod-1.loc.example.com.au hostname => vmhost-prod-1 So the 127.0.1.1 line in /etc/hosts could be used as a workaround. I can't add in vmhost-prod-1 to the 127.0.1.1 line - it must be the FQDN only, if I do.. facter ipaddr reports the fake loopback address instead of the IPv6 address. facter -p ipaddress 127.0.1.1 Add Comment   Facter / FACT-168 Changed domain and fqdn facts I just updated a bunch of RHEL6 systems from facter 1.6.18 to 1.7.2, and for some reason the domain and fqdn facts have changed. I think it's related to the fix in issue #20938, since all of the servers affected have non-resolvable hostnames. Before : {code} [root@d01 ~]# facter domain fqdn hostname domain => evo.example.com fqdn => d01.evo.examp... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.