Jira (FACT-1885) Facter doesn't like the notify flag on routing table entries

[Jon Schewe (JIRA)]

Title: Message Title

Jon Schewe created an issue   Facter / FACT-1885 Facter doesn't like the notify flag on routing table entries Issue Type: Bug Affects Versions: FACT 3.10.0 Assignee: Unassigned Created: 2018/09/19 6:18 AM Environment: Ubuntu Linux 18.04 >uname -a Linux bbn-11838 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux >apt show puppet Package: puppet Version: 5.4.0-2ubuntu3  >facter --version 3.10.0 Priority: Normal Reporter: Jon Schewe I see from FACT-1405 that you've fixed this particular issue for nexthop flags, but not for all flags. I cam across the following errors for the notify flag. Could this fix be expanded to handle all flags in the routing table? puppet-agent[32368]: (Facter) Could not process routing table entry: Expected a destination followed by key/value pairs, got 'default via XXX.XXX.XXX.XXX dev eno1 proto unspec notify' puppet-agent[32368]: (Facter) Could not process routing table entry: Expected a destination followed by key/value pairs, got 'XXX.XXX.XXX.XXX/24 dev eno1 proto unspec scope link metric 100 notify' 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. For more options, visit https://groups.google.com/d/optout.