Description of problem: As of now user is able to create arbiter volume from UI but general tab of the volume needs to be modified to show Number of bricks for an arbiter volume and brick tab should have a label indicating which of the brick is arbiter in the volume. Volume Name: engine Type: Replicate Volume ID: 6ddf5c6d-419f-4efe-8d8d-008a96eb1bf5 Status: Started Snapshot Count: 0 Number of Bricks: 1 x (2 + 1) = 3 Transport-type: tcp Bricks: Brick1: 10.70.36.79:/rhgs/brick1/engine Brick2: 10.70.36.80:/rhgs/brick1/engine Brick3: 10.70.36.81:/rhgs/brick1/engine (arbiter) gluster volume info displays as above. So it would be good to show number of bricks in the same format in volume general tab plus indicate which bricks is arbiter. Version-Release number of selected component (if applicable): ovirt-engine-4.1.0-0.3.beta2.el7.noarch How reproducible: Always Steps to Reproduce: 1. Create an arbiter volume from cli or UI 2. 3. Actual results: Number of bricks are shown as '3' and there is no indication in the bricks tab about which of the brick is arbiter. Expected results: Number of bricks should be shown in the format of how it is represented in gluster cli and there should be an indication in the bricks sub tab about which is an arbiter brick. Additional info:
Following changes where made as part of fixing this bug. 1. Replica count will be changed to 2+1 in case of Arbiter volume. 2. Volume type will have a arbiter flag 3. All arbiter bricks will have arbiter flag in the brick path.
Agreed with the Gluster team we can move Gluster bugs to ON_QA on engine build.
Verified and works fine with build ovirt-engine-4.1.0.2-0.1.el7.noarch. I see that when user creates a arbiter volume from CLI or UI replica count in the general tab changes to 2+1 , volume Type is displayed as "replicate (arbiter)". I see that arbiter bricks does have arbiter flag in the brick path when the volume is created from CLI. I see that arbiter bricks does not have arbiter flag in the brick path when creating a arbiter volume from UI. Logged another bug https://bugzilla.redhat.com/show_bug.cgi?id=1417101 for that and marking this as verified.