Bug#918250: Facter: Could not process routing table entry: Expected a destination followed by key/value pairs

2019-07-07 Thread Miquel van Smoorenburg 
I ran into the same problem. It looks like it only happens on hosts with 
IPv6 enabled.


I found a workaround for hosts where the IPv6 address is configured 
statically in /etc/network/interfaces.


The workaround is to remove the 'onlink' attribute from the route, which 
can be done reasonably easy by adding one "up" command to any static entry:


iface eth0 inet6 static
    address 2001:0db8:85a3::7a/64
    gateway 2001:0db8:85a3::1
    dad-attempts 0
    # dirty hack. removes 'onlink' attribute. works around #918250.
    up ip -6 r change default via $IF_GATEWAY

HTH

Mike.

Bug#918250: Facter: Could not process routing table entry: Expected a destination followed by key/value pairs

2019-07-04 Thread Moritz Muehlenhoff 
severity 918250 important
thanks

On Fri, Jan 04, 2019 at 07:57:42PM +0100, Bernhard Schmidt wrote:
> Package: facter
> Version: 3.11.0-1.1
> Severity: minor
> 
> After upgrading a test-VM from Stretch to Buster the following error appears
> with every puppet run
> 
> Warning: Facter: Could not process routing table entry: Expected a 
> destination followed by key/value pairs, got 'default via fe80::1 dev ens18 
> metric 1024 onlink pref medium'
> 
> root@opsvm:~# ip -6 route
> ::1 dev lo proto kernel metric 256 pref medium
> 2001:1b10:100:3::/64 dev ens18 proto kernel metric 256 pref medium
> fe80::/64 dev ens18 proto kernel metric 256 pref medium
> default via fe80::1 dev ens18 metric 1024 onlink pref medium
> 
> This is most likely
> 
> https://tickets.puppetlabs.com/browse/FACT-1885

Hi Puppet maintainers,
after the upgrade to facter 3.11 at the Wikimedia Foundation (from the 
ruby-based 2.4.6 in Stretch)
we've run into the same on a number of servers; Puppet runs have become quite 
spammy, see below for
example output from a Puppet run on one of our Varnish cache hosts:

A colleague of mine (CCed) tracked this down to 
https://tickets.puppetlabs.com/browse/FACT-1916 and
submitted a patch which got merged to the 3.11 branch as
https://github.com/puppetlabs/facter/commit/0e089f585362fa508caed5af598d615d0da24d05

The patch is self-contained and seems like a sensible candidate for a Buster 
point update once fixed
in unstable? If you agree, I'd be happy to do the legwork of preparing a Buster 
update and proposing
an update to the stable release team.

Cheers,
Moritz


% sudo puppet agent -t  
   [10:23:31]
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.0.130 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.0.132 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.16.22 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.16.24 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.32.67 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.32.69 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.48.101 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.64.48.103 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.0.122 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.0.125 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.0.127 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.16.133 via 10.20.0.1 dev eno1  mtu 
lock 1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.16.136 via 10.20.0.1 dev eno1  mtu 
lock 1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.16.138 via 10.20.0.1 dev eno1  mtu 
lock 1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.32.112 via 10.20.0.1 dev eno1  mtu 
lock 1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.32.115 via 10.20.0.1 dev eno1  mtu 
lock 1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.48.23 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '10.192.48.27 via 10.20.0.1 dev eno1  mtu lock 
1450'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got '2620:0:860:101:10:192:0:122 via fe80::1 dev 
eno1 metric 1024  mtu lock 1450 pref medium'
Warning: Facter: Could not process routing table entry: Expected a destination 
followed

Bug#918250: Facter: Could not process routing table entry: Expected a destination followed by key/value pairs

2019-01-04 Thread Bernhard Schmidt 
Package: facter
Version: 3.11.0-1.1
Severity: minor

After upgrading a test-VM from Stretch to Buster the following error appears
with every puppet run

Warning: Facter: Could not process routing table entry: Expected a destination 
followed by key/value pairs, got 'default via fe80::1 dev ens18 metric 1024 
onlink pref medium'

root@opsvm:~# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:1b10:100:3::/64 dev ens18 proto kernel metric 256 pref medium
fe80::/64 dev ens18 proto kernel metric 256 pref medium
default via fe80::1 dev ens18 metric 1024 onlink pref medium

This is most likely

https://tickets.puppetlabs.com/browse/FACT-1885

Bernhard