Description of problem: Currently all of brick, gsyncd and other glustershd services/processes are killed without checking for ongoing tasks such as geo-rep, self-heal, rebalance and etc. which may lead to inconsistency after the node is brought back. Version-Release number of selected component (if applicable): mainline Actual results: inconsistency in data Expected results: Smooth resume with no data inconsistency
Considering this is not done in last 3 years, moving it to DEFERRED, assuming this is not critical.