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

Private ipaddress is used as ipaddress fact

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Won't Fix
    • FACT 1.7.4, FACT 2.4.0, FACT 2.4.6
    • FACT 2.4.5
    • None
    • None
    • 2
    • Client 2016-01-13, Client 2016-01-27
    • Reviewed
    • Bug Fix
    • Hide
      Previously, Facter would use the first interface returned by 'ifconfig' as the primary interface for the ipaddress/macaddress/netmask facts.

      On Linux. It now determines the primary interface by looking for the default route and using the interface specified there.
      Show
      Previously, Facter would use the first interface returned by 'ifconfig' as the primary interface for the ipaddress/macaddress/netmask facts. On Linux. It now determines the primary interface by looking for the default route and using the interface specified there.

    Description

      After adding docker interface all servers have the same :ipaddress fact. It seems that Facter is using the very first alphabetically sorted interface as the primary one.

      docker0 Link encap:Ethernet HWaddr 12:de:2d:b1:9d:14
      inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0

      eth0 Link encap:Ethernet HWaddr 00:25:90:d1:d1:7a
      inet addr: ...

      I think facter should ignore private addresses if there is an interface with a public ipaddress.

      https://github.com/deric/puppet-mesos/pull/1

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              deric Tomas Barton
              Votes:
              13 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support