Bug 1351675 - Heketi allows to delete heketidbstorage volume without any warning
Summary: Heketi allows to delete heketidbstorage volume without any warning
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: rhgs-3.1
Hardware: Unspecified
OS: Unspecified
high
urgent
Target Milestone: ---
: RHGS Container Converged 1.0
Assignee: Luis Pabón
QA Contact: Neha
URL:
Whiteboard:
Depends On:
Blocks: 1332128
TreeView+ depends on / blocked
 
Reported: 2016-06-30 14:33 UTC by Neha
Modified: 2016-11-08 22:25 UTC (History)
7 users (show)

Fixed In Version: v2.0.4-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-04 04:51:58 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1498 0 normal SHIPPED_LIVE heketi update for Red Hat Gluster Storage 3.1 2016-08-04 08:49:19 UTC

Description Neha 2016-06-30 14:33:03 UTC 
Heketi does not give any warning before deleting the db volume. It will crash the running container.

[kubeexec] DEBUG 2016/06/30 10:28:41 /src/github.com/heketi/heketi/executors/kubeexec/kubeexec.go:301: Host: glusterfs-dc-dhcp43-36.lab.eng.blr.redhat.com-1-oq6hx Command: sudo sed -i.save '/brick_9bf1613ebb7ff4e217f5e3c702af5992/d' /var/lib/heketi/fstab
Result: 
unexpected fault address 0x7ff35a90f000
fatal error: fault
[signal 0x7 code=0x2 addr=0x7ff35a90f000 pc=0x639827]
Comment 2 Neha 2016-06-30 14:34:27 UTC 
upstream issue https://github.com/heketi/heketi/issues/403
Comment 6 Neha 2016-07-18 09:09:09 UTC 
heketi-cli volume delete 2301722cb8681192ce07ec92825e0a9b
Error: Cannot delete volume containing the Heketi database

logs:

[negroni] Started DELETE /volumes/2301722cb8681192ce07ec92825e0a9b
[negroni] Completed 409 Conflict in 341.099µs


Verified from backend too.
Comment 8 errata-xmlrpc 2016-08-04 04:51:58 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, 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://rhn.redhat.com/errata/RHBA-2016-1498.html
Note You need to log in before you can comment on or make changes to this bug.