Bug 698771

Summary: better handling for server shutdown while long running tasks are active
Product: [Retired] 389 Reporter: Rich Megginson <rmeggins>
Component: Directory ServerAssignee: Rich Megginson <rmeggins>
Status: CLOSED UPSTREAM QA Contact: Chandrasekar Kannan <ckannan>
Severity: high Docs Contact:
Priority: high    
Version: 1.2.8CC: andrey.ivanov, benl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.2.10.a7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 781533 (view as bug list) Environment:
Last Closed: 2012-02-07 16:14:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 690319, 781533    

Description Rich Megginson 2011-04-21 18:01:29 UTC 
We need to better handle the case where a server is shutdown while a long running task is active e.g. fixup-memberof.

Tasks should check to see if the server is shutdown and gracefully exit.

For some tasks that will leave the database in a inconsistent state, we could do one of two things:

1) the server will refuse to shutdown until all tasks are finished
2) the server will print an ugly error message to the log: "hey, you killed me before I could finish task X - the database will be in an inconsistent state until you let the task complete"
Comment 3 Martin Kosek 2012-01-04 13:23:59 UTC 
Upstream ticket:
https://fedorahosted.org/389/ticket/49
Comment 4 Rich Megginson 2012-02-07 16:14:46 UTC 
Fixed in version 1.2.10.a7