Bug 1665386
| Summary: | heketi device deletion command is deleting vg when we are executing delete command without disabling and removing the device | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Pulkit Kundra <pkundra> |
| Component: | heketi | Assignee: | John Mulligan <jmulligan> |
| Status: | CLOSED ERRATA | QA Contact: | Nitin Goyal <nigoyal> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | ocs-3.11 | CC: | akrishna, arukumar, hchiramm, jmulligan, kramdoss, madam, nigoyal, rhs-bugs, sankarshan, storage-qa-internal |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | OCS 3.11.z Batch Update 2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | heketi-8.0.0-9.el7rhgs | Doc Type: | Bug Fix |
| Doc Text: |
Previously, if the "heketi-cli device delete" sub-command was run for a device that contained no bricks before the device was disabled and removed, the underlying volume group was removed but the device remained in the Heketi database. This led to devices that required the --force-forget flag to be removed cleanly. Now, Heketi does not change the state of the underlying device until the state of the device in Heketi is correct.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-03-27 04:55:35 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: | |||
|
Comment 11
Anjana KD
2019-03-19 04:29:42 UTC
(In reply to Anjana from comment #11) > Hi John, > > Kindly check the updated doc text. Looks OK to me. 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/RHBA-2019:0663 |