Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-10972

puppet facts diff produces unexpected results

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved
    • Normal
    • Resolution: Fixed
    • None
    • None
    • None
    • Night's Watch
    • 1
    • NW - 2021-04-28, NW - 2021-05-19
    • Needs Assessment
    • Not Needed
    • Needs Assessment

    Description

      Puppet Version: 6.21.1
      Puppet Server Version:  2019.8.2.92
      OS Name/Version: RHEL8.3

      Observing failures and discrepancies while running puppet facts diff

      Example of a failure :

      # puppet facts diff
      E, [2021-03-23T15:10:50.151056 #1607340] ERROR -- : Facter - Error while resolving custom fact fact='java_version', resolution='<anonymous>': undefined method `include?' for nil:NilClass
      

      The error comes from https://github.com/puppetlabs/puppetlabs-java/blob/main/lib/facter/java_version.rb#L40, which should not be evaluated on RHEL, so confine statements are ignored, it seems

      Example of a discrepancy:

      # puppet facts diff
      ...
        "platform_tag": {
          "new_value": "redhat-8-x86_64",
          "old_value": "el-8-x86_64"
        },
      ...
      

       But if you compare output of puppet facts find, the values seems to be consistent

      # puppet facts find | grep platform_tag
          "platform_tag": "el-8-x86_64",
      # puppet facts find --facterng |grep platform_tag
      WARN: Unresolved specs during Gem::Specification.reset:
            ffi (~> 1.9)
      WARN: Clearing out unresolved specs.
      Please report a bug if this causes problems.
          "platform_tag": "el-8-x86_64",
      
      

       

       

      Attachments

        Issue Links

          Activity

            People

              luchian.nemes Luchian Nemes
              vchepkov Vadym Chepkov
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support