Bug 1598685 - After deleting all pvs creating new volume fails with no space error; Heketi topology info shows free space =0 on all devices
Summary: After deleting all pvs creating new volume fails with no space error; Heketi ...
Keywords:
Status: CLOSED DUPLICATE of bug 1584191
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: ---
: ---
Assignee: Raghavendra Talur
QA Contact: vinutha
URL:
Whiteboard:
Depends On:
Blocks: 1568862
TreeView+ depends on / blocked
 
Reported: 2018-07-06 08:06 UTC by vinutha
Modified: 2018-08-03 11:27 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-08-03 11:27:36 UTC
Embargoed:


Attachments (Terms of Use)

Description vinutha 2018-07-06 08:06:04 UTC
Description of problem:
After creating and deleting 20 file and 20 block pvs. There are no volumes present except heketidbstorage as per heketi cli command. However, further volume creation fails with error 'No space to allocate new volume' 

Version-Release number of selected component (if applicable):
# oc rsh heketi-storage-1-fn45d 
sh-4.2# rpm -qa| grep heketi
python-heketi-7.0.0-2.el7rhgs.x86_64
heketi-client-7.0.0-2.el7rhgs.x86_64
heketi-7.0.0-2.el7rhgs.x86_64


How reproducible:
Always on this setup

Steps to Reproduce:
1.
2.
3.

Actual results:
Volume creation fails and heketi topology info shows used space=0 for almost all devices  

Expected results:
Volume creation should succeed and heketi topology should display correct space free and used space. 

Additional info:
Heketi logs, heketi db dump, journalctl logs, heketi topology, oc-events attached

Comment 8 Raghavendra Talur 2018-08-03 11:27:36 UTC
Root cause:
Some of the volumes failed to create because of https://bugzilla.redhat.com/show_bug.cgi?id=1599803
Therefore rollback was tried, but because of the rollback bug(https://bugzilla.redhat.com/show_bug.cgi?id=1584191) the space on the devices wasn't corrected. 

As the root cause is same as the other bug, I will mark this a duplicate.

*** This bug has been marked as a duplicate of bug 1584191 ***


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