Bug 1331586 - [GSS](6.4.z) ageout-history does not report failures
Summary: [GSS](6.4.z) ageout-history does not report failures
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Patching
Version: 6.4.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.12
Assignee: Bartek Spyrko-Smietanko
QA Contact: Jan Martiska
URL:
Whiteboard: eap6412-proposed
Depends On:
Blocks: eap6412-payload
TreeView+ depends on / blocked
 
Reported: 2016-04-28 21:39 UTC by dereed
Modified: 2019-10-10 12:01 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 13:12:43 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEAP-4542 0 Major Closed ageout-history does not report failures 2018-06-13 13:25:58 UTC
Red Hat Issue Tracker WFLY-6572 0 Major Resolved ageout-history does not report failures 2018-06-13 13:25:58 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.