Description of problem: When Heketi is terminated while working on an operation (for example, volume create) or Heketi is unable to roll back an operation at the time of failure (for example, volume can not be created or removed from gluster) it leaves the operation behind in the heketi db. Leaving this data behind is useful because it will enable the server to resolve the issues in the future. However, this feature for using this data to resolve the issues later has not yet been implemented. This bug exists to provide an overall goal of using these db entries to "automatically" reconcile the entries with the backend storage subsystem. Additional info: The feature set can be broken down into a rough list of items: * Ability to revert/clean up stale or failed pending operations ** Covered operations: volume create/delete/expand, block volume create/delete ** Not initially covered: device or node replace (for this release) * On heketi server start clean up operations automatically * Periodic clean up of operations (on long running server) * Commands for: ** Manually kick off an operation cleanup (all) ** Manually kick off cleanup of a specific operation (by id) ** Command to list operations and their statuses Items in the above list may be broken down into individual BZs for tracking purposes.
Updated doc text. Kindly verify for Technical accuracy.
Thankyou for pointing that out.
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, 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/RHEA-2019:0286