Bug 1331586

Summary: [GSS](6.4.z) ageout-history does not report failures
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: dereed
Component: PatchingAssignee: Bartek Spyrko-Smietanko <bspyrkos>
Status: CLOSED CURRENTRELEASE QA Contact: Jan Martiska <jmartisk>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.4.6CC: bmaxwell, brian.stansberry, bspyrkos, jason.greene, jawilson, jbilek, jdoyle, jtruhlar, kconner, msimka, olubyans, ppalaga
Target Milestone: CR1   
Target Release: EAP 6.4.12   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: eap6412-proposed
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-17 13:12:43 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: 1375585    

Description dereed 2016-04-28 21:39:29 UTC 
When ageout-history cannot delete the old CP files, it silently fails and returns "success".

LocalAgeoutHistoryHandler#recursiveDelete does keep track of whether the
delete failed or succeeded, but the return value from this method is ignored
in execute(...).

If recursiveDelete returns false, it should report a failure.
Comment 1 JBoss JIRA Server 2016-04-29 13:12:25 UTC 
Bartosz Spyrko-Śmietanko <spyrkob> updated the status of jira WFLY-6572 to Coding In Progress
Comment 3 JBoss JIRA Server 2016-08-23 11:38:47 UTC 
Jiri Pallich <jpallich> updated the status of jira JBEAP-4542 to Closed
Comment 5 Jiří Bílek 2016-11-04 11:59:08 UTC 
Verified with EAP 6.4.12.CP.CR1
Comment 6 Petr Penicka 2017-01-17 13:12:43 UTC 
Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.