Bug 1638316
| Summary: | heketi is giving error on deletion of block device "Error: Volume 2be96a5cba8e68184eb0e488934ab75c free size may not be set greater than 100" | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Nitin Goyal <nigoyal> |
| Component: | heketi | Assignee: | John Mulligan <jmulligan> |
| Status: | CLOSED ERRATA | QA Contact: | Ashmitha Ambastha <asambast> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | ocs-3.11 | CC: | asambast, hchiramm, jmulligan, kramdoss, madam, rhs-bugs, rtalur, sankarshan, storage-qa-internal, suprasad |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | OCS 3.11 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | heketi-7.0.0-15.el7rhgs | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-24 04:51:02 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: | 1629581 | ||
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 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 |
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