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

Facter 4 outputs ldom facts differently on Solaris SPARC

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: FACT 4.1.0
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Night's Watch
    • Story Points:
      2
    • Sprint:
      NW - 2021-03-31, NW - 2021-04-14
    • Method Found:
      Manual Test
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Fix an issue where Facter 4 reported boolean values as strings for Solaris LDOM facts. The values are now represented as boolean, similar to the Facter 3 behavior.
    • QA Risk Assessment:
      Needs Assessment

      Description

      Running puppet facts diff on Solaris 11 SPARC gives the following output:

              "hypervisors.ldom.role_control": {
                "new_value": "false",
                "old_value": false
              },
              "hypervisors.ldom.role_io": {
                "new_value": "false",
                "old_value": false
              },
              "hypervisors.ldom.role_root": {
                "new_value": "false",
                "old_value": false
              },
              "hypervisors.ldom.role_service": {
                "new_value": "false",
                "old_value": false
              },
      

      This may be due to how Facter 3 represents boolean values in general, as ldom facts appear to be strings when placed in the collection: https://github.com/puppetlabs/facter/blob/3.x/lib/src/facts/solaris/ldom_resolver.cc#L55

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              gabriel.nagy Gabriel Nagy
              Reporter:
              luchian.nemes Luchian Nemes
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support