Bug 1351675

Summary:	Heketi allows to delete heketidbstorage volume without any warning
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Neha <nerawat>
Component:	heketi	Assignee:	Luis Pabón <lpabon>
Status:	CLOSED ERRATA	QA Contact:	Neha <nerawat>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	rhgs-3.1	CC:	annair, hchiramm, madam, mliyazud, pprakash, rcyriac, sashinde
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS Container Converged 1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	v2.0.4-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-04 04:51:58 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:	1332128

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