Bug 884598
| Summary: | Alert definitions are missing after JBoss is imported in JON | |||
|---|---|---|---|---|
| Product: | [Other] RHQ Project | Reporter: | bkramer <bkramer> | |
| Component: | Core Server | Assignee: | RHQ Project Maintainer <rhq-maint> | |
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | 4.4 | CC: | bkramer, hrupp, jshaughn, loleary | |
| Target Milestone: | --- | |||
| Target Release: | RHQ 4.13 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 884593 | |||
| : | 884593 (view as bug list) | Environment: | ||
| Last Closed: | 2014-09-03 19:28:56 UTC | Type: | Bug | |
| 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: | 884593 | |||
|
Description
bkramer
2012-12-06 11:15:57 UTC
This sounds like it may be a duplicate of Bug 969535. I recommend testing this again with RHQ 4.8 or later. If the test still fails please let me know. (In reply to Jay Shaughnessy from comment #1) > This sounds like it may be a duplicate of Bug 969535. I recommend testing > this again with RHQ 4.8 or later. > > If the test still fails please let me know. I run the test using RHQ 4.9.0 and the same issue still exists - alert definition from the alert template is not added to the JBoss resource when the agent is restarted with --cleanconfig. If --cleanconfig is not used (just regular restart) then alert definition is added. Starting the agent --cleanconfig implicitly performs --purgedata, which deletes the agent's data directory. By doing so the agent now has to get its inventory from the server. That means that the resources are all considered previously UNKNOWN by the agent. When bringing up the agent normally the resources would already be known to the agent, and be in the NEW state. In the latter case we can see that the the resources have moved from NEW to COMMITTED when syncing with the server are startup. As such we perform newly-committed resource actions, including alert template application. For UNKNOWN resources we don't know the previous state and basically assume that a COMMITTED resource was previously committed and should not have the newly-committed actions applied. This is a fair assumption as this will be the case in any scenario other the the current scenario, where not only was the agent down at import time but was also brought up --cleanconfig (or --purgedata). The problem with changing this behavior is that if we apply the templates we could be undoing work performed by the users, who may have altered the previously applied templates and now would get them again just due to an agent restart. The workaround here would just be to uninventory the problematic resource(s) and re-import them with the agent running, or with the agent later brought up normally. Unless there is some common use-case for the scenario causing this problem I think this should be closed as won't fix, and the workaround used as necessary. Bump the target version now that 4.11 is out. I still think this should be closed/wontfix but for now bumping to 4.13 for further triage. I'm closing this as Not A Bug. It's a deep corner case, the behavior is as expected, and it has reasonable workarounds: - uninventory and re-import - manually update the template and have it re-applied to the existing inventory. |