Bug 1577803 - [RFE] heketi is not showing expected error when we give same name of the vol.
Summary: [RFE] heketi is not showing expected error when we give same name of the vol.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: rhgs-3.3
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: OCS 3.11.z Batch Update 4
Assignee: John Mulligan
QA Contact: Nitin Goyal
URL:
Whiteboard:
: 1652876 (view as bug list)
Depends On: 1707789
Blocks: OCS-3.11.1-Engineering-Proposed-BZs OCS-3.11.1-devel-triage-done
TreeView+ depends on / blocked
 
Reported: 2018-05-14 07:30 UTC by Nitin Goyal
Modified: 2020-01-03 04:39 UTC (History)
10 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-10-30 12:34:04 UTC
Embargoed:

Attachments (Terms of Use)
logs for comment 8 (255.37 KB, application/zip)
2019-01-24 11:00 UTC, krishnaram Karthick 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2019:3255 0 None None None 2019-10-30 12:34:25 UTC

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
Note You need to log in before you can comment on or make changes to this bug.