Issue #21808 has been updated by Matthias Saou.
Actually, downgrading to 1.7.1 doesn't fix my issue. I still get the different domain and fqdn facts. Downgrading to 1.6.18, which I previously had before updating to 1.7.2, does get me the old values back (which are the ones I expect to have). ---------------------------------------- Bug #21808: Changed domain and fqdn facts https://projects.puppetlabs.com/issues/21808#change-94956 * Author: Matthias Saou * Status: Unreviewed * Priority: Normal * Assignee: * Category: * Target version: 1.7.3 * Keywords: * Branch: * Affected Facter version: 1.7.2 ---------------------------------------- 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> [root@d01 ~]# facter domain fqdn hostname domain => evo.example.com fqdn => d01.evo.example.com hostname => d01 </pre> After : <pre> [root@d01 ~]# facter domain fqdn hostname domain => evo.example.lan fqdn => d01.evo.example.lan hostname => d01 </pre> While this hasn't changed : <pre> [root@d01 ~]# hostname d01.evo.example.com </pre> 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> [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> 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> [root@d01 ~]# cat /etc/resolv.conf search evo.example.lan evo.example.com nameserver 192.168.12.254 </pre> If I remove it, to leave only "search evo.example.com", then I get this : <pre> [root@d01 ~]# facter domain fqdn hostname domain => fqdn => hostname => d01 </pre> 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> [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> -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
