Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1690850 - [cockpit] Brick size is incorrect after user modifies the volume from arbiter to pure replica.
Summary: [cockpit] Brick size is incorrect after user modifies the volume from arbiter...
Status: NEW
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: rhhi
Version: rhhiv-1.6
Hardware: x86_64
OS: Linux
Target Milestone: ---
: ---
Assignee: Sahina Bose
Depends On: 1690880
TreeView+ depends on / blocked
Reported: 2019-03-20 10:51 UTC by Mugdha Soni
Modified: 2019-04-11 07:57 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1690880 (view as bug list)
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)
Arbiter screenshot (deleted)
2019-03-20 10:51 UTC, Mugdha Soni
no flags Details

Description Mugdha Soni 2019-03-20 10:51:28 UTC
Created attachment 1546004 [details]
Arbiter screenshot

Description of problem:
If the user has the arbiter-replicate volume and later modifies it to pure replicate then the LV size in the third host picks up the default size and not the previous modified size by the user .

Version-Release number of selected component :


How reproducible:
Every time

Steps to Reproduce:
1.Log in to cockpit UI and fill in all the required parameters till volume tab. 
2.Change the LV size in bricks tab .
3.Then press the back button and and uncheck the arbiter checkbox for the volume 
  and then check the LV size for that brick on third host .

Actual results:
The LV size of the modified volume is  reflected as the default value and not a modified value by the user .

Expected results:
The LV size of the modified volume should be the changed size from the user an d not the default size.

Additional info:
If the user set vmstore volume as the arbiter-replicate and the change the LV size from 500GB (default) to 7126GB and then goes back and modifies the type from arbiter-replicate to pure replicate , the LV size in the third host for vmstore will be taken as the default value i.e 500GB and not the modified size.

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