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

Facter fails "closed" if the facter.conf file is invalid

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FACT 4.0.50
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Night's Watch
    • Story Points:
      2
    • Sprint:
      NW - 2021-02-03
    • Method Found:
      Needs Assessment
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      Description of the problem: Facter fails when an invalid config file is provided.

      Description of the fix: Log a warning message stating that the parsing of config file failed and continue retrieving facts with the default options.
      Show
      Description of the problem: Facter fails when an invalid config file is provided. Description of the fix: Log a warning message stating that the parsing of config file failed and continue retrieving facts with the default options.
    • QA Risk Assessment:
      Needs Assessment

      Description

      With facter 4 shipped with puppet 7.1 if the facter.conf file is invalid facter fails to load at all which prevents all subsequent puppet runs. 

       

      This means that instead of being able to fix the problem with a puppet run the administrator has to login to any affected server and fix the file by hand.  

      Would it be possible to fail "open" if the file is invalid?  Log an error and run with all defaults?  This would at least allow puppet to fix the problem on a subsequent run.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              oana.tanasoiu Oana Tanasoiu
              Reporter:
              tparker@cbnco.com Tom Parker
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support