Bug 1812122

Summary: Improve the reliability of device remove
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: John Mulligan <jmulligan>
Component: heketiAssignee: John Mulligan <jmulligan>
Status: CLOSED ERRATA QA Contact: Vinayak Papnoi <vpapnoi>
Severity: high Docs Contact: Amrita <asakthiv>
Priority: unspecified    
Version: ocs-3.11CC: aramteke, asakthiv, hchiramm, madam, nigoyal, pprakash, puebele, rhs-bugs, rtalur, storage-qa-internal, susgupta, vpapnoi
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.z Batch Update 6   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: heketi-9.0.0-12 Doc Type: Enhancement
Doc Text:
With this update, Heketi’s device remove operation is fully tracked and based on a series of brick eviction operations , thereby making the overall process much more reliable. Heketi used to track an operation for overall device replacement but that operation did not track the underlying changes Heketi was making to volumes as part of a device remove operation. When an error was encountered during the device remove operation, the lack of detailed tracking could have lead to database inconsistency with Gluster, creating a need to manually repair the database.
 Story Points: ---
Clone Of:
: 1850072 (view as bug list) Environment:
Last Closed: 2020-12-17 04:31:42 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: 1630172    
Bug Blocks: 1850072    

Description John Mulligan 2020-03-10 14:56:06 UTC 
Description of problem:

The last large action customers take using heketi that is not based on reliable operations metadata is 'device remove' / 'device replace'. Changing this to be based on operations would greatly improve the reliability of the system and allow the heketi auto-clean behavior to assist with keeping the db in a good state.


In theory this would reduce the number of times support team would need assistance from developers and avoid having to edit the db as json.
Comment 18 errata-xmlrpc 2020-12-17 04:31:42 UTC 
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 (OpenShift Container Storage 3.11.z bug fix update), 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://access.redhat.com/errata/RHBA-2020:5602