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

Facter crashes when attempting to return an empty array

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: FACT 3.0.2
    • Fix Version/s: FACT 3.1.1
    • Component/s: PE, Windows
    • Labels:
      None
    • Environment:

      Reported with Windows 2008R2 in PE 2015.2.0 virtual machines.

    • Template:
    • Story Points:
      1
    • Sprint:
      Client 2015-10-28
    • CS Priority:
      Needs Priority
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      When resolving dmi facts on Windows, if WMI is unable to resolve the Win32_ComputerSystemProduct's Name, Win32_Bios's SerialNumber or Manufacturer it would previously throw an exception and halt the Facter run. It will now fail to resolve specific dmi facts without halting Facter.
      Show
      When resolving dmi facts on Windows, if WMI is unable to resolve the Win32_ComputerSystemProduct's Name, Win32_Bios's SerialNumber or Manufacturer it would previously throw an exception and halt the Facter run. It will now fail to resolve specific dmi facts without halting Facter.

      Description

      Customer reports that intermittently at a rate of about once a week, puppet runs will stall with the following error:

      C:\Windows\system32>puppet agent -t
      Info: Retrieving pluginfacts
      Info: Retrieving plugin
      Info: Loading facts
      terminate called after throwing an instance of 'facter::util::windows::wmi_exception'
      what(): unable to get from empty array of objects
      

      Facter debug output reveals the following additional details:

      Debug: Facter: resolving desktop management interface facts.
      terminate called after throwing an instance of 'facter::util::windows::wmi_exception'
      what(): unable to get from empty array of objects
       
      This application has requested the Runtime to terminate it in an unusual way.
      Please contact the application's support team for more information. 
      

      The workaround at this point is to reboot the VM.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                john.duarte John Duarte
                Reporter:
                erik.hansen Erik Hansen
                QA Contact:
                Eric Thompson
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support