Bug 1597349 - Heketi volume deletion fails with error 'Volume does not exist' but heketi lists info of the same volume
Summary: Heketi volume deletion fails with error 'Volume does not exist' but heketi li...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: cns-3.10
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: CNS 3.10
Assignee: Michael Adam
QA Contact: vinutha
URL:
Whiteboard:
Depends On:
Blocks: 1568862
TreeView+ depends on / blocked
 
Reported: 2018-07-02 17:15 UTC by vinutha
Modified: 2018-12-20 09:53 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-12 09:23:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2018:2686 0 None None None 2018-09-12 09:25:05 UTC

Description vinutha 2018-07-02 17:15:14 UTC
Description of problem:
Heketi volume deletion fails with error 'Volume does not exist' but heketi lists info of the same volume 

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

How reproducible:
Always 

Steps to Reproduce:
1. On a CNS 4 node setup have 10 file volumes of 10GB present 
2. Create and delete block and file volumes - no discrepancy observed 
3. Reboot the heketi pod 
4. Create 40 file volumes in loop. 
5. Delete the file volumes except heketidb 
6. Observe that all file volumes are not deleted however from gluster end no volumes are present except heketidb. 

Actual results:
Error: Unable to delete volume vol_e83a4d94567494c1ce327a7c793ecd27: Unable to execute command on glusterfs-storage-8jp55: volume delete: vol_e83a4d94567494c1ce327a7c793ecd27: failed: Volume vol_e83a4d94567494c1ce327a7c793ecd27 does not exist

Expected results:
Heketi volume deletion should be successful

Additional info:

Comment 20 errata-xmlrpc 2018-09-12 09:23:49 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/RHEA-2018:2686


Note You need to log in before you can comment on or make changes to this bug.