Bug 725736 - [augeas] components should return null from loadConfiguration if augeas is not present instead of throwing an exception
Summary: [augeas] components should return null from loadConfiguration if augeas is no...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: RHQ Project
Classification: Other
Component: Plugins
Version: 4.1
Hardware: Unspecified
OS: Unspecified
medium
unspecified vote
Target Milestone: ---
: RHQ 4.9
Assignee: Heiko W. Rupp
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks: jon30-bugs
TreeView+ depends on / blocked
 
Reported: 2011-07-26 12:26 UTC by Lukas Krejci
Modified: 2014-03-26 08:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-03-26 08:31:01 UTC


Attachments (Terms of Use)


Links
System ID Priority Status Summary Last Updated
Red Hat Bugzilla 725740 None None None Never

Internal Links: 728292

Description Lukas Krejci 2011-07-26 12:26:58 UTC
Description of problem:

Many of our augeas-based plugins throw an exception from their loadResourceConfiguration() methods when augeas is not available. 

We should consider changing this behavior to just returning null (and thus suggesting that configuration is "disabled") for the following reasons:

1) we don't spam the agent log with load config failure messages
2) the configuration is really technically just disabled because of the lack of support of augeas

Note that this is only of any importance on non-RHEL systems for which we don't bundle augeas native libraries.


How reproducible:
always

Steps to Reproduce:
1. install agent on AIX or some other UNIX-like system (that doesn't have augeas installed)
2. inventory it 
3. Try going to the Configuration tab of the Sudoers resource
  
Actual results:
exception

Expected results:
no exception because the configuration is merely disabled.

Additional info:

Comment 1 Heiko W. Rupp 2013-06-29 07:36:23 UTC
See also Bug 979658

Comment 2 Heiko W. Rupp 2013-06-29 14:31:55 UTC
master 2b75b3367e03

Also suppress some stacktraces that are just clobbering the logs

Comment 3 Heiko W. Rupp 2014-03-26 08:31:01 UTC
Bulk closing now that 4.10 is out.

If you think an issue is not resolved, please open a new BZ and link to the existing one.


Note You need to log in before you can comment on or make changes to this bug.