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

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

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