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

facts.d module "external" facts get put in client dir which facter doesn't look at by default

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Won't Fix
    • FACT 2.2.0
    • None
    • None
    • None

    • Facter 2.2.0
      Puppet 3.6.2
      CentOS 6.5

    Description

      Fact scripts placed in the recommended path of <MODULEPATH>/<MODULE>/facts.d/ get added to clients into the /var/lib/puppet/facts.d directory, but then this directory is only searched for .rb ruby fact snippets by default.

      If facter is run explicitly as:

      facter --external-dir /var/lib/puppet/facts.d/ <factname>

      ..then this works fine, as does lookup of the facts in puppet manifests.

      However, this seems non-sensical and that the facter default should be to look in the directory which fact scripts are placed into automatically; especially as this is the recommended method of adding external script facts via module magic sync rather than placing them into /etc/facter/facts.d explicitly.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. FACT-957 module facts.d sync'd to agent not shown in facter -p output

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

          Bug - A problem which impairs or prevents the functions of the product. PUP-3610 external facts copied over via pluginsync dont show up when facter runs

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

          Task - A task that needs to be done. FACT-96 Deprecate 'facter --puppet'

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

          Bug - A problem which impairs or prevents the functions of the product. PUP-7082 External Facts are not loading when kept inside a module

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Activity

            People

              Unassigned Unassigned
              legooolas David Gardner
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support