Issue #15990 has been updated by Christian Kruse.
It seems as if parser options have been introduced with libxml-ruby 1.1.3 (see http://libxml.rubyforge.org/rdoc/files/HISTORY.html). The easy and IMHO safer solution would be to defer to use a libxml-ruby not having LibXML::XML::Parser::Options::NOBLANKS: begin require dirname + '/rbLibXMLParser.rb' temp = LibXML::XML::Parser::Options::NOBLANKS; # check if we have a version with parser options try_nokogiri = false rescue LoadError => e try_nokogiri = true end If you are agree, I would create a new and patched version of CFPropertyList. ---------------------------------------- Bug #15990: Puppet fails due to facter error on 10.5.8 clients https://projects.puppetlabs.com/issues/15990#change-70591 Author: Chris Barker Status: Needs More Information Priority: Normal Assignee: Chris Barker Category: Target version: Keywords: cfpropertylist xml plist parse Branch: Affected Facter version: 2.0.0rc3 Running on ruby 1.8.6, it appears that CFPropertyList is not returning a proper plist, or is just full of null values. Trace: Error: Could not run: Could not retrieve facts for 10-5-8-pl-vm.local: undefined method `each' for nil:NilClass /Users/puppet/src/facter/lib/facter/macosx.rb:30 The line is: Facter::Util::Macosx.hardware_overview.each do |fact, value| Putting test code in place, it appears that around line 30/31 in facter/utils/macosx.rb the call to CFPropertList::List.new is returning nil values, so it might be a rexml issue in rbCFTypes util/macosx.rb: plist = Facter::Util::CFPropertyList::List.new begin plist.load_str(xml) rescue => e fail("A plist file could not be properly read by Facter::Util::CFPropertyList: #{e.inspect}") end The plist.load_str(xml) never appears to return. I am working with Gary on this, so I will update as we dig into this more. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
