These are the new features, resolved issues, and deprecations in this version of Facter.
For Facter releases later than version 3.11.x, release notes are included in the corresponding Puppet documentation set. For the most recent Facter documentation, see the Facter page.
Released 14 January 2020
This release adds support for the
fips_enabled fact on Windows. The check examines the contents of
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Control/Lsa/FipsAlgorithmPolicy/Enabled. If the returned value is 1, it means that FIPS mode is enabled. FACT-2065
Facter can now return the new
scope6 fact to display IPv6 address scope. FACT-2016
Facter command execution now accepts a Boolean parameter,
expand. By default, Facter searches the command and expands it to absolute path. When
expand is set to false, Facter verifies whether the command is a shell command and, if so, passes the command as is.FACT-1824
Facter incorrectly reported disabled CPU cores as physical CPU cores. Now, Facter correctly reports physical and logical CPUs and ignores disabled CPUs. FACT-1824
In previous releases, Facter did not report the
cloud fact on Azure. This issue is now fixed. FACT-2004
In previous versions, Facter could not always determine the primary network interface on Solaris, so it sometimes failed to return any valid interface. This is now fixed. FACT-2146
-In systems using Windows Remote Desktop Services (RDS), Facter returned an incorrect operating system fact. This was due to a Windows API deprecation that caused issues in mixed 32- and 64-bit application environments, such as RDS. FACT-2096
Released 15 October 2019 with Puppet 5.5.17.
Google Compute Engine’s internal metadata service is deprecating the v1beta1 endpoint sometime before the end of 2019. To prepare for this, Facter now uses the v1 endpoint instead. FACT-2018
When Facter starts a mountpoint to get the size and available space, it automatically mounts type
autofs mountpoints, which is not the intended behavior. Automounts are now skipped by Facter when resolving mountpoints. FACT-1992
Released 16 July 2019 with Puppet 5.5.16.
This release adds new facts for Windows 10/2016+ :
ReleaseID: The 4 digit Windows build Version in the form
InstallationType: Differentiates Server, Server Core, Client (Desktop):
EditionID: Server or Desktop Edition variant:
ProductName: Textual Product Name.
Exception: on Windows 10 1511-x86_64,
ReleaseID is not displayed, as is not present in Windows registry. FACT-1881
ip route showoutput was not in a key-value format. However, this format does not apply to all configurations, and Facter no longer returns warnings about this. FACT-1916
mountpointfact showed only temporary file systems and physical mounts. Now Facter returns mount points for all mounts on the systems. FACT-1910
Released 16 April 2019
os.release) on Ubuntu systems that did not have the
lsb_releaseexecutable. Operating system facts are now resolved without relying on
Released 15 January 2019
This is a bug-fix release that shipped with Puppet Platform 5.5.10
Released 1 November 2018
This is a bug-fix release that shipped with Puppet Platform 5.5.8
Released 23 October 2018
This is a bug-fix release that shipped with Puppet Platform 5.5.7.
Released 21 August 2018
This is a bug-fix release that shipped with Puppet Platform 5.5.6.
Facter now indicates if SELinux is enabled on the system by also checking for the existence of the
/etc/selinux/config file in addition to checking for the presence of the SELinux file system. (FACT-1477)
Facter returned the wrong IPv6 information when IPV6 stack was disabled. Now,Facter correctly validates the IP command’s output for the IPv6 family. If the IP command’s output is invalid (for example, if it contains IPv4 info), then Facter ignores it. (FACT-1475)
Facter failed on Solaris 11.3 patch 126.96.36.199 native zone. Now, Facter does not try to read kstat entries that it does not need to process. This avoids potential permissions issues when run in a zone or as non-root on Solaris. (FACT-1832)
Facter has been updated to correctly read the format of
/etc/system-release under Amazon Linux 2. This corrects the operating system release fact, which previously fell back to the kernel version. (FACT-1865)
os.architecture fact is now determined from the
processors.models fact. This addresses a problem where Puppet agent wasn’t working with dynamic CPU allocations on AIX. (FACT-1550)
memory fact was occasionally failing on AIX. This has been fixed. (FACT-1821)
Released July 17, 2018.
This is a bug-fix release that shipped with Puppet Platform 5.5.4.
Facter 3.11.3 correctly reads the format of
/etc/system-release and reports the
os release fact on Amazon Linux 2. Previous versions of Facter instead fell back to the kernel version. (FACT-1865)
Facter 3.11.3 no longer tries to read
kstat entries that it does not need to process. This avoids potential permissions issues when run in a zone or as non-root on Solaris. (FACT-1832)
Released June 7, 2018.
This is a bug-fix release that shipped with Puppet Platform 5.5.2 and 5.5.3.
When using the
systemd-networkd DHCP client, previous versions of the Linux networking resolver didn’t know how to collect DHCP lease information, since it expected
dhclient to be installed. Systems relying entirely on
systemd-networkd for DHCP management do not use
Facter 3.11.2 checks
systemd-networkd’s DHCP leases directory (
/run/systemd/netif/leases) in addition to
dhclient’s lease files when attempting to identify DHCP servers.
Released April 17, 2018.
This is a bug-fix and feature release that shipped with Puppet Platform 5.5.1.
Facter 3.11.1 properly checks for errors when gathering disk information on AIX, and no longer warns or reports bogus results for devices assigned to special uses, such as databases. (FACT-1597)
Facter 3.11.1 reports MAC addresses on infiniband interfaces. (FACT-1761)
Released March 20, 2018.
This is a bug-fix and feature release that shipped with Puppet Platform 5.5.0.
uptimefact for Windows now uses
GetTickCount64, which is more reliable, minimizes clock skews, and offers better resolution than the previous method of computing using WMI BootUptime.