Jira (PUP-10799) networking.interfaces fact not appearing

3 views
Skip to first unread message

Chris Boot (Jira)

unread,
Dec 3, 2020, 7:41:03 AM12/3/20
to puppe...@googlegroups.com
Chris Boot created an issue
 
Puppet / Bug PUP-10799
networking.interfaces fact not appearing
Issue Type: Bug Bug
Affects Versions: PUP 7.0.0
Assignee: Unassigned
Attachments: facter-networking-interfaces.log, facter-networking-primary.log, facter-networking.log
Created: 2020/12/03 4:40 AM
Priority: Normal Normal
Reporter: Chris Boot

Puppet Version: 7.0.0
Puppet Server Version: 6.14.1
OS Name/Version: Debian testing (bullseye)

On one of my nodes, Puppet does not pick up the networking.interfaces fact. The fact is visible when querying Facter directly for the top-level fact (e.g. facter networking) but does not show up through Puppet (e.g. puppet facts show networking) or when querying the sub-fact value (e.g. facter networking.interfaces).

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Josh Cooper (Jira)

unread,
Dec 3, 2020, 6:08:04 PM12/3/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
Change By: Josh Cooper
Labels: platform_7.1

Josh Cooper (Jira)

unread,
Dec 3, 2020, 6:29:03 PM12/3/20
to puppe...@googlegroups.com
Josh Cooper commented on Bug PUP-10799
 
Re: networking.interfaces fact not appearing

The facter-networking-interfaces.log shows:

 167   │ [2020-12-03 12:38:53.226174 ] DEBUG Facter::Resolvers::NetworkingLinux - fill_ip_v4_info!
 168   │ [2020-12-03 12:38:53.226538 ] DEBUG Facter::Util::FileHelper - File at: /run/systemd/netif/leases/53 is not accessible.
 169   │ [2020-12-03 12:38:53.228884 ] DEBUG Facter::Core::Execution::Posix - Executing command: ip route get 1
 170   │ [2020-12-03 12:38:53.243479 ] DEBUG Facter::Resolvers::NetworkingLinux - resolving fact interfaces, but undefined method `each' for nil:NilClass

The ip route get 1 is coming from https://github.com/puppetlabs/facter/blob/fd9beb8e809e3c6ef5f43af409d77e20396a5044/lib/facter/resolvers/networking_linux_resolver.rb#L145. Something goes wrong after that happens. It doesn't appear --trace works for core facts, so I'm not sure how to get a backtrace...

Reply all
Reply to author
Forward
0 new messages