Bug 1592649 - free size in block hosting volume info isn't updated on expansion
Summary: free size in block hosting volume info isn't updated on expansion
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: cns-3.10
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: CNS 3.10
Assignee: Raghavendra Talur
QA Contact: Neha Berry
URL:
Whiteboard:
Depends On:
Blocks: 1568862
TreeView+ depends on / blocked
 
Reported: 2018-06-19 04:36 UTC by Raghavendra Talur
Modified: 2018-11-20 06:43 UTC (History)
12 users (show)

Fixed In Version: heketi-7.0.0-2.el7rhgs
Doc Type: Bug Fix
Doc Text:
Previously, If the block hosting volume was expanded free space attribute of the volume was not updated leading to block volume failures even though space was available.With this fix, free size in block hosting volume information is updated.
Clone Of:
Environment:
Last Closed: 2018-09-12 09:23:45 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:24:56 UTC

Description Raghavendra Talur 2018-06-19 04:36:14 UTC 
Description of problem:

Kind of issue
Bug

Observed behavior
When a block hosting volume is expanded then the free size isn't updated.

Expected/desired behavior
Free size should get updated

Details on how to reproduce (minimal and precise)
create a block volume
block hosting volume should get auto created
now expand the block hosting volume
try creating a block volume which would cross the original limit of block hosting volume

Information about the environment:
heketi 7
Comment 2 Raghavendra Talur 2018-06-19 04:37:18 UTC 
Patch posted at https://github.com/heketi/heketi/pull/1231
Comment 4 Anjana KD 2018-08-30 23:50:42 UTC 
Updated doc text in the Doc Text field. Please review for technical accuracy.
Comment 5 John Mulligan 2018-09-07 17:24:36 UTC 
Doc Text looks OK
Comment 7 errata-xmlrpc 2018-09-12 09:23:45 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.