Bug 1346624

Summary:	Minimum brick size error
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Neha <nerawat>
Component:	heketi	Assignee:	Michael Adam <madam>
Status:	CLOSED DUPLICATE	QA Contact:	Sachin <sashinde>
Severity:	low	Docs Contact:
Priority:	low
Version:	rhgs-3.1	CC:	madam, mzywusko, pprakash, sashinde
Target Milestone:	---	Keywords:	Reopened, 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:	2016-10-01 00:29:10 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 Neha 2016-06-15 06:20:41 UTC

Current error message for minimum size brick

heketi-cli volume create --size=1
Error: No space

[heketi] ERROR 2016/06/14 02:41:06 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:41: Minimum brick size limit reached. Out of space.
[negroni] Started GET /queue/8d662515743827d44875d9bf146d0f19
[negroni] Completed 200 OK in 73.023µs

Should be somewhat similar to logs "Minimum brick size limit reached" instead of "No space"

upstream bug: https://github.com/heketi/heketi/issues/380

Comment 2 Luis Pabón 2016-07-06 16:30:19 UTC

No, you are viewing this from a GlusterFS point of view.  From a "volume" point of view, however it is implemented, there is no space.

Comment 3 Neha 2016-07-07 04:46:43 UTC

If in a cluster we have enough space on each of the node. Then getting "No Space" error is not correct.

It failed to create volume because we are giving volume size less than "Minimum volume size/Brick size limit" and that's the error getting logged in the heketi logs.

[heketi] ERROR 2016/06/14 02:41:06 /src/github.com/heketi/heketi/apps/glusterfs/volume_entry_allocate.go:41: Minimum brick size limit reached. Out of space.
[negroni] Started GET /queue/8d662515743827d44875d9bf146d0f19
[negroni] Completed 200 OK in 73.023µs

I believe the same error should be displayed to stdout to avoid confusion.

Comment 6 Michael Adam 2016-10-01 00:12:10 UTC

Issue seems to be a duplicate of https://github.com/heketi/heketi/issues/506

and it has been fixed with https://github.com/heketi/heketi/pull/536 .

Comment 7 Michael Adam 2016-10-01 00:13:42 UTC

This is actually imho pretty much the same BZ as https://bugzilla.redhat.com/show_bug.cgi?id=1352778

Comment 8 Michael Adam 2016-10-01 00:29:10 UTC


*** This bug has been marked as a duplicate of bug 1370130 ***