Bug 535401 (RHQ-2100)
Summary: | group operations not timing out - still INPROGRESS | ||
---|---|---|---|
Product: | [Other] RHQ Project | Reporter: | John Mazzitelli <mazz> |
Component: | Core UI | Assignee: | John Mazzitelli <mazz> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | cwelton, rtimaniy, skondkar |
Target Milestone: | --- | Keywords: | SubBug |
Target Release: | --- | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://jira.rhq-project.org/browse/RHQ-2100 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-05-24 01:13:30 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: | 697001 | ||
Bug Blocks: | 585306 |
Description
John Mazzitelli
2009-05-20 14:24:00 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-2100 Temporarily adding the keyword "SubBug" so we can be sure we have accounted for all the bugs. keyword: new = Tracking + FutureFeature + SubBug making sure we're not missing any bugs in rhq_triage ONQA per triage. If this is still an issue, reopen, otherwise close. Tested on RHQ-Master build#438 http://hudson-qe.rhq.rdu.redhat.com:8080/view/RHQ/job/ci-rhq-master/438/ It looks like group operation is still not implemented, need to retest once group operation gets implemented. this is possibly related to bug #697001 - I'm putting this issue on the rhq4 blocks list so we can test it along with that 697001 one. That said, I have seen the group operation history item get timed out. However, 697001 is indicating that the individual resource items are not getting timed out. commit 7f4f22446b9d692e191415f612a40f0f23d42b89 if for some reason (usually due to a bug) a resource op history is in INPROGRESS for a really long time, we now flip the status to FAILURE after 1 day of bring in that inprogress state. Also, there was a bug in one of our queries that affected group ops that also is fixed in the above commit. This issue should therefore be fixed. Verified on build#39 (Version: 4.0.0-SNAPSHOT Build Number: 15a53e5) Started two agents on the same box, then imported both their platforms, then shutdown the first and kept the second one up. Created a compatible group consisting of both platform resources. Navigated to the group's operation tab and executed one of the platform's operations. (Followed the steps provided in bug#697001) The status of the group operation shows failed. Marking as verified. Bookkeeping - closing bug - fixed in recent release. Bookkeeping - closing bug - fixed in recent release. Bookkeeping - closing bug - fixed in recent release. |