Bug 535659 (RHQ-2331)
Summary: | content discovery doesn't happen for 12 hours after initial import | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
Component: | Plugin Container | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Corey Welton <cwelton> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | Keywords: | Improvement |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jira.rhq-project.org/browse/RHQ-2331 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
John Mazzitelli
2009-08-11 15:59:00 UTC
it seems like the reasonable thing to do would be to reschedule for now when you enable it. this doesn't just cover the disable->enable case, but also the enable->enable case. doing this will allow users a nifty trick to "force" the discovery by making a no-op change to active configs (or enabling currently disabled configs). note, when you reschedule it, it should cancel current schedules and basically reset the 12-hr clock from the point of enablement. RHQ-2332 is tangentially related - deals with content scheduling too one problem is that the inventory event listener had hooks for ACTIVATING resources but curiously did not have hooks for handling DEACTIVATING resources. so it never got rid of schedules for resources whose components were stopped. I'll be adding this to the listener framework. QA Verified, initial content discovery no longer takes 12 hours. This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2331 This bug is related to RHQ-2332 |