Bug 1690880

Summary:	Brick size is incorrect after user modifies the volume from arbiter to pure replica.
Product:	[oVirt] cockpit-ovirt	Reporter:	Mugdha Soni <musoni>
Component:	gluster-ansible	Assignee:	Parth Dhanjal <dparth>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	0.12.5	CC:	bugs, dparth, godas, gzaidman, lsvaty, rhs-bugs, sabose, sasundar
Target Milestone:	ovirt-4.4.0	Flags:	sbonazzo: ovirt-4.4?
Target Release:	0.14.1
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	cockpit-ovirt-0.14.1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1690850	Environment:
Last Closed:	2020-05-20 20:00:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Gluster	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1690850

Description Mugdha Soni 2019-03-20 11:43:50 UTC

+++ This bug was initially created as a clone of Bug #1690850 +++

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 :
-----------------------------------------------
glusterfs-server-3.12.2-47.el7rhgs
gluster-ansible-repositories-1.0-1.el7rhgs.noarch
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
gluster-ansible-features-1.0.4-5.el7rhgs.noarch
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
gluster-ansible-roles-1.0.4-4.el7rhgs.noarch
gluster-ansible-infra-1.0.3-3.el7rhgs.noarch

rhvh-4.3.0.5-0.20190313


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.

Comment 2 Sandro Bonazzola 2020-01-23 12:21:35 UTC

All referenced patches have been merged, can this bug move to modified?
A build including referenced patches have been issued, can this move to ON_QA?

Comment 4 SATHEESARAN 2020-03-30 14:09:59 UTC

Tested with cockpit-ovirt-dashboard-0.14.3
1. Started HC deployment with 3 nodes
2. Populate storage network and public network FQDN
3. On volumes tab, go with the default list of gluster volumes.
4. Select 'arbiter' for 'data' volume
5. Go to bricks tab, check for the size of the 'data' volume's brick on the third host.
This will be 20GB, as the volume is of type 'arbiter'
6. Go to previous tab - 'Volumes' tab and deselect 'arbiter', so volume type is replicate
7. Now proceed to 'volumes' tab and check for the size of 'data' volume's brick on third host
This size is same as the size of other bricks

Comment 5 Sandro Bonazzola 2020-05-20 20:00:24 UTC

This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.