Jira (FACT-168) Changed domain and fqdn facts

[Eric Sorenson (JIRA)]

Title: Message Title

Eric Sorenson updated an issue   Facter / FACT-168 Changed domain and fqdn facts Change By: Eric Sorenson 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 : <pre> {code} [root@d01 ~]# facter domain fqdn hostname domain => evo.example.com fqdn => d01.evo.example.com hostname => d01 </pre> {code} After : <pre> {code} [root@d01 ~]# facter domain fqdn hostname domain => evo.example.lan fqdn => d01.evo.example.lan hostname => d01 </pre> {code} While this hasn't changed : <pre> {code} [root@d01 ~]# hostname d01.evo.example.com </pre> {code} The *.lan name isn't configured anywhere inside /etc. The only place it appears is as the reverse IPv4 mapping of the server's only IPv4 address. <pre> {code} [root@d01 ~]# ip addr show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00     inet 127.0.0.1/8 scope host lo     inet6 ::1/128 scope host         valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 50:50:00:12:23:34 brd ff:ff:ff:ff:ff:ff     inet6 2001:ffff:ffff:1:1::5/64 scope global         valid_lft forever preferred_lft forever     inet6 fe80::5050:ff:1234:abcd/64 scope link         valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000 link/ether 50:50:00:12:23:35 brd ff:ff:ff:ff:ff:ff     inet 192.168.12.5/24 brd 192.168.12.255 scope global eth1     inet 192.168.12.101/24 scope global secondary eth1     inet6 fe80::5050:ff:1234:abcf/64 scope link         valid_lft forever preferred_lft forever </pre> {code} The next thing I found is that I do have the evo.example.lan domain in one single place (grepping for .lan in /etc) : <pre> {code} [root@d01 ~]# cat /etc/resolv.conf search evo.example.lan evo.example.com nameserver 192.168.12.254 </pre> {code} If I remove it, to leave only "search evo.example.com", then I get this : <pre> {code} [root@d01 ~]# facter domain fqdn hostname domain =>  fqdn =>  hostname => d01 </pre> {code} Downgrading from facter 1.7.2 to 1.7.1 now gives the correct answer, whatever the content of /etc/resolv.conf, but the warnings are back : <pre> {code} [root@d01 ~]# facter domain fqdn hostname hostname: No address associated with name dnsdomainname: No address associated with name domain => evo.example.lan fqdn => d01.evo.example.lan hostname => d01 </pre> {code} Add Comment   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/groups/opt_out.