Bug 1724992

Summary:	heketi is trying to create a blockvolume with the same name.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nitin Goyal <nigoyal>
Component:	heketi	Assignee:	John Mulligan <jmulligan>
Status:	CLOSED WONTFIX	QA Contact:	Nitin Goyal <nigoyal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	hchiramm, jmulligan, knarra, kramdoss, madam, prasanna.kalever, rhs-bugs, rtalur, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-09-06 16:51:16 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:

Description Nitin Goyal 2019-06-28 08:36:59 UTC

Description of problem:
heketi is trying to create a blockvolume of same name even-though volume of same name is already there. 

If blockvolume with the same name is already present heketi should not try to create a blockvolume. heketi should pre-check its db for the same name of blockvolume.

The similar issue is fixed for file volume bz 1577803.

Version-Release number of selected component (if applicable):
heketi-cli 9.0.0-2.el7rhgs

How reproducible:


Steps to Reproduce:
1. heketi-cli blockvolume create --size 1 --name vol
2. heketi-cli blockvolume create --size 1 --name vol
3.

Actual results:

Expected results:

Additional info:

Comment 2 John Mulligan 2019-06-28 13:39:59 UTC

Logs please.

Comment 4 John Mulligan 2019-07-01 14:25:04 UTC

I checked the behavior of heketi wrt re-using the same name of a block volume. Heketi is designed to support multiple block volumes with the same name as long as those block volumes are unique to a block hosting volume. Put another way, the system will create a new block hosting volume (when possible) if the user requests the exact same name for block volumes.

I see one error in the log and it is coming from gluster block itself and it's not clear that the error has anything to do with the name. If you wish to go deeper on that error let me know. Otherwise, I'd say the system is working as designed.