Bug 535021 (RHQ-1760)
Summary: | Group config update when agent is down, never completes, blocks further config edits | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | Jeff Weiss <jweiss> |
Component: | Configuration | Assignee: | Ian Springer <ian.springer> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Jeff Weiss <jweiss> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.2 | CC: | ccrouch, dajohnso |
Target Milestone: | --- | Keywords: | SubBug |
Target Release: | --- | Flags: | jweiss:
archived+
|
Hardware: | All | ||
OS: | All | ||
URL: | http://jira.rhq-project.org/browse/RHQ-1760 | ||
Whiteboard: | |||
Fixed In Version: | 1.2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
rev3351
|
|
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: | |||
Bug Depends On: | |||
Bug Blocks: | 534605 |
Description
Jeff Weiss
2009-03-10 18:51:00 UTC
This also seems to permanently disable any further viewing or updating of the config for that group, even when the agent comes back. Upping priority. Workaround: delete the in-progress event history item. lowering priority. The Server has a reaper job that should time out defunct group config updates (i.e. updates where the Agent went down in the middle of the update) after 10-20 minutes. If you see the update still in the history after the Agent has been down for > 20 minutes, then there's an issue. Otherwise, things are working as intended. I know i waited at least 30 minutes before, I just repeated the test, it's been 1 hour 20 minutes now, still "In Progress". It's definitely broken. r3451 fixes this - the CheckForTimedOutConfigUpdatesJob Quartz job will now time out group config update requests that were initiated more than 11 minutes ago. I repeated the procedure on rev3509, still says in progress after more than 15 minutes. <ips> jweiss: in worst case, it may take as long as 22 mins for the server to time out the group request; if it takes longer than that, something's wrong It took over 15 minutes, so this did actually pass. closing. This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1760 This bug is related to RHQ-1632 |