Uploaded image for project: 'Facter'
  1. Facter
  2. FACT-1885

Facter doesn't like the notify flag on routing table entries

    XMLWordPrintable

Details

    • Bug
    • Status: Accepted
    • Normal
    • Resolution: Unresolved
    • FACT 3.10.0
    • None
    • None
    • Platform OS
    • Needs Assessment
    • Needs Assessment

    Description

      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'

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. FACT-1405 Facter does not like next hop flags in ip route output

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Activity

            People

              Unassigned Unassigned
              jschewe Jon Schewe
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:

                Zendesk Support