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

Running 'facter --puppet' produced no warning/debug messages

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Fixed
    • FACT 3.1.0
    • FACT 3.1.1
    • None
    • None
    • 2
    • Client 2015-10-28
    • Bug Fix
    • Hide
      Facter with the `--puppet` option causes Puppet to be initialized in the Ruby VM hosted by Facter. Part of Puppet's initialization process is to configure Facter's logging. This resulted in unintentionally changing Facter's logging such that log messages were no being displayed. This has been corrected so that Facter respects its initial logging configuration.
      Show
      Facter with the `--puppet` option causes Puppet to be initialized in the Ruby VM hosted by Facter. Part of Puppet's initialization process is to configure Facter's logging. This resulted in unintentionally changing Facter's logging such that log messages were no being displayed. This has been corrected so that Facter respects its initial logging configuration.

    Description

      The change for FACT-750 introduced pluggable logging, which is used by puppet/master currently. As an unintended side effect facter --puppet ends up giving puppet a chance to register its default loggers, but they do nothing when run as facter. The net result is that no facter debug/warning output is seen on the command line.

      The fix might be to deregister puppet's handlers forcibly after the require 'puppet' when facter is handling --puppet.

      Otoh, facter --puppet is going to be deprecated in facter 3, per FACT-96, so the lifetime of this bug should be short regardless.

      Attachments

        Issue Links

          Activity

            People

              john.duarte John Duarte
              kylo Kylo Ginsberg
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support