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

Facter warns aboutIt difficulty parsing routing entries on Fedora 24

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Duplicate
    • None
    • None
    • None
    • None

    Description

      Under some circumstances (such as when running libvirtd with the standard NAT network, or any situation where the route output includes "linkdown"), Facter complains about not being able to parse route output:

      2016-07-19 19:04:33.871180 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got '192.168.6.0/24 dev br6 proto kernel scope link src 192.168.6.1 metric 425 linkdown'
      2016-07-19 19:04:33.872683 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'fe80::/64 dev br6 proto kernel metric 256 linkdown pref medium'

      Here is the ip route output:

      192.168.1.0/24 proto zebra metric 20
      nexthop via 192.168.5.2 dev br5 weight 1
      nexthop via 192.168.5.3 dev br5 weight 1
      192.168.4.0/24 proto zebra metric 20
      nexthop via 192.168.5.2 dev br5 weight 1
      nexthop via 192.168.5.3 dev br5 weight 1
      192.168.5.0/24 dev br5 proto kernel scope link src 192.168.5.15 metric 425
      192.168.6.0/24 dev br6 proto kernel scope link src 192.168.6.1 metric 425 linkdown
      192.168.129.0/24 dev br900 proto kernel scope link src 192.168.129.15 metric 425

      1. rpm -qf /usr/sbin/ip
        iproute-4.4.0-3.fc24.x86_64

      It is not clear that this actually causes a problem, but the warning messages are a bit jarring.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              mjackson Martin Jackson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support