Bug 773435
Summary: | Enabled event sources cause initial resource component start to time out | |||
---|---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Jay Shaughnessy <jshaughn> | |
Component: | Agent | Assignee: | Jay Shaughnessy <jshaughn> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Mike Foley <mfoley> | |
Severity: | high | Docs Contact: | ||
Priority: | high | |||
Version: | 4.2 | CC: | bkramer, ccrouch, hrupp | |
Target Milestone: | --- | |||
Target Release: | RHQ 4.3.0 | |||
Hardware: | All | |||
OS: | All | |||
Whiteboard: | ||||
Fixed In Version: | 4.3 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 784730 (view as bug list) | Environment: | ||
Last Closed: | 2013-09-01 10:13:29 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 760116, 784730 |
Description
Jay Shaughnessy
2012-01-11 20:05:11 UTC
commit d1a4410a78bfbed7baa8b65b71abea0315a3fea0 lazily access sigar on the first polling, which happens after container initialization. Test Notes Perhaps not super-easy to test but with debug logging on the agent and and an enabled event source (enable the built in event source for the RHQ Server resource) you should see no related messages of any severity for the component startup (at agent startup time). Also, the log event generation should work as expected, generating an event for each server log entry (assuming the default settings) *** Bug 782796 has been marked as a duplicate of this bug. *** Bulk closing of items that are on_qa and in old RHQ releases, which are out for a long time and where the issue has not been re-opened since. |