Jira (FACT-1466) Facter warns aboutIt difficulty parsing routing entries on Fedora 24

2016-12-20 Thread Lee Whalen (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Lee Whalen commented on  FACT-1466 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Facter warns aboutIt difficulty parsing routing entries on Fedora 24  
 
 
 
 
 
 
 
 
 
 
This also happens on Ubuntu 16.04, with the following:  puppet-agent 1.8.2-1xenial (package) $ facter -v: 3.5.0 (commit 872c5707799c1c30925b632f20eab763ec03b5a4) $ puppet --version: 4.8.1 
$ ip route default via 172.33.0.1 dev eth0  172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown  172.33.0.0/24 dev eth0 proto kernel scope link src 172.33.0.91  
The actual warning message on my systes is:  $ facter 2016-12-21 07:53:01.621537 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got '172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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 puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (FACT-1466) Facter warns aboutIt difficulty parsing routing entries on Fedora 24

2016-07-19 Thread Martin Jackson (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Martin Jackson created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Facter /  FACT-1466 
 
 
 
  Facter warns aboutIt difficulty parsing routing entries on Fedora 24  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/07/19 5:15 PM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Martin Jackson 
 
 
 
 
 
 
 
 
 
 
Under some circumstances (such as when running libvirtd with the standard NAT network, or any situation where the route output includes "linkdown"), Facter complains about not being able to parse route output: 
2016-07-19 19:04:33.871180 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got '192.168.6.0/24 dev br6 proto kernel scope link src 192.168.6.1 metric 425 linkdown' 2016-07-19 19:04:33.872683 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'fe80::/64 dev br6 proto kernel metric 256 linkdown pref medium' 
Here is the ip route output: 
192.168.1.0/24 proto zebra metric 20  nexthop via 192.168.5.2 dev br5 weight 1 nexthop via 192.168.5.3 dev br5 weight 1 192.168.4.0/24 proto zebra metric 20  nexthop via 192.168.5.2 dev br5 weight 1 nexthop via 192.168.5.3 dev br5 weight 1 192.168.5.0/24 dev br5 proto kernel scope link src 192.168.5.15 metric 425  192.168.6.0/24 dev br6 proto kernel scope link src 192.168.6.1 metric 425 linkdown  192.168.129.0/24 dev br900 proto kernel scope link src 192.168.129.15 metric 425  
 

rpm -qf /usr/sbin/ip iproute-4.4.0-3.fc24.x86_64
 
 
It is not clear that this actually causes a problem, but the warning messages are a bit jarring.