Issue #22334 has been updated by Ethan Brown.

Affected Facter version set to 1.7.3-rc1

Initial `warn` calls crept into codebase at

* Fix #2455 - improve error handling on fact load - 3/23/2011 - 
https://github.com/puppetlabs/facter/commit/bfe8a2a9e7a03c2a09273ef74d59e2843f5359ae#lib/facter/util/resolution.rb
* Fixing #1927 - failing facts don't kill Facter - 3/23/2011 - 
https://github.com/puppetlabs/facter/commit/f4bc74d1590ab219d3589dc8c2d11acd062a3d63#lib/facter/util/resolution.rb
* Refactored so each fact resolution can specify a separate timeout - 3/23/2011 
- 
https://github.com/puppetlabs/facter/commit/d322df9a367fde290a3aa3d1b15082939c8fff19#lib/facter/util/resolution.rb

----------------------------------------
Bug #22334: Facter outputs information to stderr irrespective of whether 
--debug is enabled
https://projects.puppetlabs.com/issues/22334#change-97163

* Author: Andrew Parker
* Status: Merged - Pending Release
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 1.7.4
* Keywords: 
* Branch: https://github.com/puppetlabs/facter/pull/529
* Affected Facter version: 1.7.3-rc1
----------------------------------------
When a fact resolution raises an error, Facter will output a message of the 
format `"Could not retrieve %s: %s" % [self.name, details]`. This message is 
output using ruby's native `warn` method instead of Facter's `warn` method 
which is controlled by `--debug`. This same method is used when a fact file 
fails to load, and when a fact takes too long. At the very least Facter needs 
to be using its own logging system in order to avoid outputting to stderr when 
it shouldn't.


-- 
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 unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to