Bug 1638316 - heketi is giving error on deletion of block device "Error: Volume 2be96a5cba8e68184eb0e488934ab75c free size may not be set greater than 100"
Summary: heketi is giving error on deletion of block device "Error: Volume 2be96a5cba8...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 3.11
Assignee: John Mulligan
QA Contact: Ashmitha Ambastha
URL:
Whiteboard:
Depends On:
Blocks: 1629581
TreeView+ depends on / blocked
 
Reported: 2018-10-11 10:38 UTC by Nitin Goyal
Modified: 2019-08-20 05:02 UTC (History)
10 users (show)

Fixed In Version: heketi-7.0.0-15.el7rhgs
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-10-24 04:51:02 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github heketi heketi issues 1397 0 None None None 2018-10-12 07:27:34 UTC
Red Hat Product Errata RHBA-2018:2986 0 None None None 2018-10-24 04:51:57 UTC

Description Nitin Goyal 2018-10-11 10:38:05 UTC 
Description of problem: 
block devices are deleted from gluster but entries are still there in heketi blockvolume list. 



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


How reproducible:


Steps to Reproduce:
1. Create 40 block pvcs.
2. delete them all in one shot (e.g. oc delete claim{1..40})
3. wait for some time & check the output of pv
4. there will be some entries in pv's
5. delete those pv's all in one shot
6. wait for some time & check the output of "heketi-cli blockvolume list"
7. there will be some entries in blockvolume list
8. delete all of them in one shot
9. You will get this error 
"Error: Volume 2be96a5cba8e68184eb0e488934ab75c free size may not be set greater than 100"


Actual results:
blockVolumes are still there in heketi.

Expected results:
volumes should be deleted in heketi
Comment 5 John Mulligan 2018-10-11 22:13:45 UTC 
I can confirm the existence of the issue. I was also able to reproduce with a shell for loop, such as:
$ for _ in $(seq 1 5); do ./heketi-cli blockvolume delete c5edeb20be9a55f758966d1106b5343e & done
Volume c5edeb20be9a55f758966d1106b5343e deleted
Volume c5edeb20be9a55f758966d1106b5343e deleted
Volume c5edeb20be9a55f758966d1106b5343e deleted
Volume c5edeb20be9a55f758966d1106b5343e deleted
Volume c5edeb20be9a55f758966d1106b5343e deleted

The repeated deletes are not correct and there should only be one delete message. The others should all be "conflict" or "not found" errors.

The root problem actually exists in both volumes and block volumes, however volumes do not fail completely because the file volume's bricks actually catch the conflict condition. Block volumes do not have any other matching components, so they are not accidentally protected.

More details at upstream issue: https://github.com/heketi/heketi/issues/1397
Comment 15 errata-xmlrpc 2018-10-24 04:51:02 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/RHBA-2018:2986
Note You need to log in before you can comment on or make changes to this bug.