Description of problem: Current version family of Facter 2.4 doesn't entirely support IPv6 The netmask6 facts are missing. This can be reproduced: 1. Install facter # yum install -y facter 2.By default IPv6 is active and at least the loopback interface (::1) should be set: # ip addr show lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3. Try to obtain a netmask6 fact # facter netmask6_lo Actual results: Nothing is returned Expected results: # facter netmask6_lo ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
*** This bug has been marked as a duplicate of bug 1283387 ***
I'm reopening this one because this specifically for RDO where BZ#1283387 is for RHOS (OSP). That said I can't find a facter component in RDO. It's more likely Openstack Repos to provide facter 3.x before vanilla RHEL/CENTOS/Fedora will have it.
Facter 3+ facts --------------- There are many new facts in Facter 3. Facter 3.1 contains much more facts than Facter 2.4: http://docs.puppetlabs.com/facter/2.4/core_facts.html https://docs.puppetlabs.com/facter/3.0/core_facts.html Also the facts are now structured by default (still accessible the standard way) Also Facter 3.1 is the recommended version to use for the Puppet open source version while Facter 4.1 is the one for Puppet Enterprise 3.8 Backporting ----------- I'm not sure netmask6 can be backported to 2.4, seems like there are many issues around ipv6 and some of them might be structural. On the long run we need to get going with Facter 3 anyway. Build ----- It might effectively take a while until Fedora/EPEL repos provides Facter3, this is why, as we have been doing before, make the package available as part of Openstack Repos. Note: To build latest Facter version 3.1.1, I had to use Fedora because it requires boost version >= 1.54
After some dependencies reorganisation around BZ#1280523, BZ#=1283387 and BZ#1283387, this one can be closed. *** This bug has been marked as a duplicate of bug 1283387 ***