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

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

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Accepted
    • Priority: Normal
    • Resolution: Unresolved
    • Affects Version/s: FACT 3.10.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Environment:
    • Template:
    • Team:
      Platform OS
    • Method Found:
      Needs Assessment
    • QA Risk 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

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              jschewe Jon Schewe
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:

                  Zendesk Support