Bug 1548157
Summary: | [GSS] heketi db keeps trying to remove thin pool which is already removed | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Olek Toborek <atoborek> |
Component: | heketi | Assignee: | Raghavendra Talur <rtalur> |
Status: | CLOSED ERRATA | QA Contact: | Rachael <rgeorge> |
Severity: | medium | Docs Contact: | |
Priority: | unspecified | ||
Version: | cns-3.6 | CC: | akrishna, hchiramm, jmulligan, madam, pprakash, rhs-bugs, rtalur, storage-qa-internal, tcarlin, vinug |
Target Milestone: | --- | ||
Target Release: | CNS 3.10 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
Previously, Heketi could not delete volumes that were fully or partially removed from the underlying storage system. Running Heketi commands such as 'heketi-cli volume delete <ID>' on a volume that was deleted from gluster failed due to synchronization issues. With this fix, Heketi volume delete functionality can incrementally delete a volume, skipping over items that have already been deleted.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2018-09-12 09:22:12 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: | |||
Bug Blocks: | 1568861, 1573420 |
Description
Olek Toborek
2018-02-22 20:57:59 UTC
Hello. That is really good news that in 3.9 it will be available, but what we can advise customer for the time being? He needs to clean up the thin pool situation, and he is looking for relief. - Olek. A possible test case for this would be: 1. create a volume using heketi 2. delete the volume using gluster 3. delete the volume using heketi Compare the user experience in a previous build and in fixed-in-version build. Updated doc text in the Doc Text field. Please review for technical accuracy. Doc Text LGTM 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-2018:2686 |