Description of problem: In OperationManagerBean on server side we have a check which marks operation histories as timed out or not started under certain conditions. Those conditions are not correct in case there is an operation with timeout larger than 24hours. Version-Release number of selected component (if applicable): JON 3.3.x How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Operation running longer than 24hours is failed on server and considered as not started Expected results: Operation should be considered as timed out after it's timeout is reached, and not started after timeout is reached and we don't have start time in given history entry. 24h limit should be removed. Additional info:
branch: master link: https://github.com/rhq-project/rhq/commit/1254b9fca time: 2015-09-22 19:31:59 +0200 commit: 1254b9fca8c3a94da2e6d8948fadfce102cbd253 author: Libor Zoubek - lzoubek message: Bug 1265309 - Operations running longer than 24hours should not be considered as not started Fix OperationManagerBean cleanup logic for IN_PROGRESS operations. The main change is, that we'll timeout only operation histories that have been started (this should mean agent received operation request) but did not finish on time (either because they just timed out or agent died in the middle of operation execution). Then we'll mark operations as not-started only if they were not started within 24hours since they were created.
Cherry-picked to release/jon3.3.x: commit 8ccd22aa13c655be8bb0b5f5e141976b2a939e70 Author: Libor Zoubek <lzoubek> Date: Tue Sep 22 18:25:46 2015 +0200 Bug 1265309 - Operations running longer than 24hours should not be considered as not started Fix OperationManagerBean cleanup logic for IN_PROGRESS operations. The main change is, that we'll timeout only operation histories that have been started (this should mean agent received operation request) but did not finish on time (either because they just timed out or agent died in the middle of operation execution). Then we'll mark operations as not-started only if they were not started within 24hours since they were created. (cherry picked from commit 1254b9fca8c3a94da2e6d8948fadfce102cbd253)
Moving to ON_QA as available to test with the following build: https://brewweb.devel.redhat.com/buildinfo?buildID=460382 *Note: jon-server-patch-3.3.0.GA.zip maps to ER01 build of jon-server-3.3.0.GA-update-04.zip.
Verified on Version : 3.3.0.GA Update 04 Build Number : e9ed05b:aa79ebd Operation is in progress longer than 24h
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1947.html