Bug 1577803

Summary: [RFE] heketi is not showing expected error when we give same name of the vol.
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nitin Goyal <nigoyal>
Component: heketiAssignee: John Mulligan <jmulligan>
Status: CLOSED ERRATA QA Contact: Nitin Goyal <nigoyal>
Severity: low Docs Contact:
Priority: low    
Version: rhgs-3.3CC: asriram, bkunal, hchiramm, jmulligan, knarra, kramdoss, nchilaka, rhs-bugs, rtalur, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.z Batch Update 4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: heketi-9.0.0-2.el7rhgs Doc Type: Bug Fix
Doc Text:
Previously, if Heketi managed multiple clusters and it failed to create volumes on any of the clusters it would return a generic "No space" error message. With this update, Heketi now displays an error message pertaining to each cluster.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-30 12:34:04 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: 1707789    
Bug Blocks: 1641685, 1641915    
Attachments:
Description Flags
logs for comment 8 none

Description Nitin Goyal 2018-05-14 07:30:34 UTC
Description of problem: I have one volume named "vol1". After that i was creating one more volume named "vol1" then it is giving me error "Error: Failed to allocate new volume: No space" although i have enough space in devices.

Version-Release number of selected component (if applicable): 6.0.0.11

How reproducible:

Steps to Reproduce:
1. $ heketi-cli volume create --name=vol1 --size=4
2. $ heketi-cli volume create --name=vol1 --size=4

Actual results: Error: Failed to allocate new volume: No space.


Expected results: Error: volume vol1 is already exsist.

Comment 9 krishnaram Karthick 2019-01-24 11:00:20 UTC
Created attachment 1523069 [details]
logs for comment 8

Comment 14 Michael Adam 2019-02-06 09:42:47 UTC
*** Bug 1652876 has been marked as a duplicate of this bug. ***

Comment 30 errata-xmlrpc 2019-10-30 12:34:04 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/RHSA-2019:3255