Jira (PUP-9721) Facter routing table process issues for Bionic on Windows

[Paul Anderson (JIRA)]

Title: Message Title

Paul Anderson created an issue   Puppet / PUP-9721 Facter routing table process issues for Bionic on Windows Issue Type: Improvement Assignee: Unassigned Created: 2019/05/25 2:07 AM Environment: Windows 10 Pro Version 1903 OS Build 18362.116 Enabled "Windows Services for Linux" Installed Ubuntu from Microsoft store installed puppet6-release-bionic.deb root@Freyir:~# apt-show-versions puppet-agent puppet-agent:amd64/bionic 6.4.2-1bionic uptodate   Priority: Normal Reporter: Paul Anderson facter > /dev/null 2019-05-25 03:03:38.127149 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 169.254.0.0/16 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.128702 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 169.254.97.104 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.130061 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 169.254.255.255 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.131062 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 224.0.0.0/4 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.132016 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 255.255.255.255 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.132991 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 224.0.0.0/4 dev eth1 proto unspec metric 256' 2019-05-25 03:03:38.133845 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 255.255.255.255 dev eth1 proto unspec metric 256' 2019-05-25 03:03:38.134670 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 127.0.0.0/8 dev lo proto unspec metric 256' 2019-05-25 03:03:38.135726 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 127.0.0.1 dev lo proto unspec metric 256' 2019-05-25 03:03:38.138659 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 127.255.255.255 dev lo proto unspec metric 256' 2019-05-25 03:03:38.139538 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 224.0.0.0/4 dev lo proto unspec metric 256' 2019-05-25 03:03:38.143289 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 255.255.255.255 dev lo proto unspec metric 256' 2019-05-25 03:03:38.144265 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none default via 10.0.1.1 dev wifi0 proto unspec metric 0' 2019-05-25 03:03:38.145245 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 10.0.1.0/24 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.146128 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 10.0.1.170 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.148691 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 10.0.1.255 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.150131 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 224.0.0.0/4 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.151046 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 255.255.255.255 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.151881 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 224.0.0.0/4 dev wifi1 proto unspec metric 256' 2019-05-25 03:03:38.152733 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none 255.255.255.255 dev wifi1 proto unspec metric 256' 2019-05-25 03:03:38.160040 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::/64 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.161177 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::e91f:4e14:130f:6168 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.163689 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none ff00::/8 dev eth0 proto unspec metric 256' 2019-05-25 03:03:38.164582 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::/64 dev eth1 proto unspec metric 256' 2019-05-25 03:03:38.165664 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::51e4:df5:d060:32b5 dev eth1 proto unspec metric 256' 2019-05-25 03:03:38.166488 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none ff00::/8 dev eth1 proto unspec metric 256' 2019-05-25 03:03:38.167328 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none ::1 dev lo proto unspec metric 256' 2019-05-25 03:03:38.169892 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none ff00::/8 dev lo proto unspec metric 256' 2019-05-25 03:03:38.171071 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::/64 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.172079 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::5006:46e5:6430:bae4 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.173415 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none ff00::/8 dev wifi0 proto unspec metric 256' 2019-05-25 03:03:38.174538 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::/64 dev wifi1 proto unspec metric 256' 2019-05-25 03:03:38.175715 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none fe80::8dc8:3ca6:92e5:4c68 dev wifi1 proto unspec metric 256' 2019-05-25 03:03:38.176482 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'none ff00::/8 dev wifi1 proto unspec metric 256' One might reasonably predict the output of ip route and ip -6 route:   root@node:~# ip route none 169.254.0.0/16 dev eth0 proto unspec metric 256 none 169.254.97.104 dev eth0 proto unspec metric 256 none 169.254.255.255 dev eth0 proto unspec metric 256 none 224.0.0.0/4 dev eth0 proto unspec metric 256 none 255.255.255.255 dev eth0 proto unspec metric 256 none 224.0.0.0/4 dev eth1 proto unspec metric 256 none 255.255.255.255 dev eth1 proto unspec metric 256 none 127.0.0.0/8 dev lo proto unspec metric 256 none 127.0.0.1 dev lo proto unspec metric 256 none 127.255.255.255 dev lo proto unspec metric 256 none 224.0.0.0/4 dev lo proto unspec metric 256 none 255.255.255.255 dev lo proto unspec metric 256 none default via 10.0.1.1 dev wifi0 proto unspec metric 0 none 10.0.1.0/24 dev wifi0 proto unspec metric 256 none 10.0.1.170 dev wifi0 proto unspec metric 256 none 10.0.1.255 dev wifi0 proto unspec metric 256 none 224.0.0.0/4 dev wifi0 proto unspec metric 256 none 255.255.255.255 dev wifi0 proto unspec metric 256 none 224.0.0.0/4 dev wifi1 proto unspec metric 256 none 255.255.255.255 dev wifi1 proto unspec metric 256 root@node:~# ip -6 route none fe80::/64 dev eth0 proto unspec metric 256 none fe80::e91f:4e14:130f:6168 dev eth0 proto unspec metric 256 none ff00::/8 dev eth0 proto unspec metric 256 none fe80::/64 dev eth1 proto unspec metric 256 none fe80::51e4:df5:d060:32b5 dev eth1 proto unspec metric 256 none ff00::/8 dev eth1 proto unspec metric 256 none ::1 dev lo proto unspec metric 256 none ff00::/8 dev lo proto unspec metric 256 none fe80::/64 dev wifi0 proto unspec metric 256 none fe80::5006:46e5:6430:bae4 dev wifi0 proto unspec metric 256 none ff00::/8 dev wifi0 proto unspec metric 256 none fe80::/64 dev wifi1 proto unspec metric 256 none fe80::8dc8:3ca6:92e5:4c68 dev wifi1 proto unspec metric 256 none ff00::/8 dev wifi1 proto unspec metric 256 Add Comment   This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310245.1558775246000.21029.1558775280505%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.