Just some additional details I found when looking at the debug output
versus the code blocks.
I don't yet know how the code for facter in networking_resolver.cc
(networking_resolver::read_routing_table() and
networking_resolver::populate_from_routing_table) need to be modified. What
I do see i
Thanks. Now I know this is a known issue. I can work with that to find a
temporary work around, somewhere. As this is a for a mgmt report I will
just drop the IP field from the hammercli and do a host lookup to populate
it.
At least this issue is not why I'm going crazy! :)
On Thursday, Octo
This looks like https://tickets.puppetlabs.com/browse/FACT-1475. We're
aware of it, but it hasn't been a priority to fix. The Facter team has
grown a bit recently, though, so I'm hopeful that we'll be able to fix
things like this more quickly in the future. Unfortunately, I still can't
say for cert
I was generating a report from Foreman using the Hammer CLI to list my
hosts for management on my Dev box. I started noticing that I wasn't seeing
any IP addresses for SUSE 11 SP3. Thinking it was a OS specific issue, I
checked my PROD environment that has a large number of SUSE 11 SP1 - SP4
be
