Bug 1607821

Summary:	heketi is creating separate block hosting volume for every block device request
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Nitin Goyal <nigoyal>
Component:	heketi	Assignee:	Michael Adam <madam>
Status:	CLOSED ERRATA	QA Contact:	krishnaram Karthick <kramdoss>
Severity:	high	Docs Contact:
Priority:	high
Version:	cns-3.10	CC:	akrishna, ekuric, hchiramm, jmulligan, kramdoss, nberry, nigoyal, pprakash, rhs-bugs, rtalur, sankarshan, storage-qa-internal
Target Milestone:	---
Target Release:	CNS 3.10
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Heketi can automatically create a new block hosting volume even when there was insufficient disk space on existing block hosting volume. Previously, if more than one request for block volumes were received concurrently Heketi might create more block hosting volumes than necessary. With this update, Heketi no longer allows clients to automatically trigger the creation of extra block hosting volumes when another request is already creating a block hosting volume.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-09-12 09:23:49 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:	1568862

Description Nitin Goyal 2018-07-24 11:02:00 UTC

Description of problem:
heketi is creating separate block hosting volumes for every block device. Because of this issue storage is also got full.

I had 9 block devices which are in pending state (in OCP) and i had 2 block hosting volumes which were all full. So there is no pending space in the existing block hosting volumes for creating new block devices. For some time all those 9 block devices are in pending state, But after some time all were bound with new 6 block hosting volumes.

Version-Release number of selected component (if applicable):
RPM: 7.0.0-4
Container: rhgs-volmanager-rhel7:3.3.1-21

How reproducible:

Steps to Reproduce:
1. Make sure you have one block hosting volume (size 100gb)
2. Create 105 block pvcs with 1gb.
3. 1 to 99 will be in bound state.
4. 100 to 105 will be in pending state.
5. After some time all 101 to 105 will be in bound state with lots of new block hosting volumes


Actual results:
heketi is creating lots of block hosting volumes.

Expected results:
heketi should create only one block hosting volume when existing block hosting volumes got full.

Additional info:

Comment 16 Michael Adam 2018-08-24 13:08:19 UTC

*** Bug 1601380 has been marked as a duplicate of this bug. ***

Comment 17 Anjana KD 2018-08-31 00:37:36 UTC

Updated doc text in the Doc Text field. Please review for technical accuracy.

Comment 19 Anjana KD 2018-09-05 04:38:17 UTC

Hi John,

I have updated the Doc text based on feedback. Kindly check.

Comment 20 John Mulligan 2018-09-05 18:16:08 UTC

(In reply to Anjana from comment #19)
> Hi John,
> 
> I have updated the Doc text based on feedback. Kindly check.

I think that's an improvement, thanks!

Comment 22 errata-xmlrpc 2018-09-12 09:23:49 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://access.redhat.com/errata/RHEA-2018:2686