Bug 1692793

Summary: [Day 2] While creating new volume or expanding the volume using day2, option to add brick should be removed
Product: [oVirt] cockpit-ovirt Reporter: Mugdha Soni <musoni>
Component: gluster-ansibleAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: Mugdha Soni <musoni>
Severity: low Docs Contact:
Priority: unspecified    
Version: 0.12.5CC: bugs, godas, rhs-bugs, sabose, sasundar
Target Milestone: ovirt-4.3.6Keywords: Regression, ZStream
Target Release: 0.13.6Flags: sasundar: ovirt-4.3?
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.13.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1692791 Environment:
Last Closed: 2019-09-26 19:43:05 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: 1692791    
Attachments:
Description Flags
screenshot for bug verification none

Description Mugdha Soni 2019-03-26 13:03:58 UTC 
+++ This bug was initially created as a clone of Bug #1692791 +++

Description of problem:
------------------------
During expand cluster in the bricks tab user has a option to add brick in brick configuration subtab.This button should be removed.


Version-Release number of selected component :
------------------------------------------------
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

glusterfs-server-3.12.2-47.el7rhgs

cockpit-ovirt-dashboard-0.12.5-1.el7ev


How reproducible:
------------------
Everytime

Steps to Reproduce:
-----------------------
1.After the successful gluster deployment ,log in to the cockpit UI and start with the expand cluster.
2.Fill in required information in all the tabs and in bricks tab the issue can be seen.

Actual results:
---------------------
Add brick button is present in bricks tab .

Expected results:
--------------------
Add brick button should not be removed as the volumes which are created in the volumes tab should only be reflected in the bricks tab and no additional brick should be created in bricks tab.

--- Additional comment from RHEL Product and Program Management on 2019-03-26 12:50:36 UTC ---

This bug report has Keywords: Regression or TestBlocker.

Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release.

Please resolve ASAP.
Comment 1 Mugdha Soni 2019-09-04 11:55:07 UTC 
Created attachment 1611478 [details]
screenshot for bug verification
Comment 2 Mugdha Soni 2019-09-04 11:56:51 UTC 
Tested with the following:-
1. rhvh-4.3.6.2-0.20190821
2.gluster-ansible-repositories-1.0.1-1.el7rhgs.noarch
glusterfs-cli-3.12.2-47.4.el7rhgs.x86_64
glusterfs-rdma-3.12.2-47.4.el7rhgs.x86_64
glusterfs-3.12.2-47.4.el7rhgs.x86_64
glusterfs-api-3.12.2-47.4.el7rhgs.x86_64
python2-gluster-3.12.2-47.4.el7rhgs.x86_64
gluster-ansible-maintenance-1.0.1-1.el7rhgs.noarch
glusterfs-events-3.12.2-47.4.el7rhgs.x86_64
vdsm-gluster-4.30.29-2.el7ev.x86_64
glusterfs-libs-3.12.2-47.4.el7rhgs.x86_64
gluster-ansible-cluster-1.0-1.el7rhgs.noarch
gluster-ansible-infra-1.0.4-3.el7rhgs.noarch
gluster-ansible-roles-1.0.5-4.el7rhgs.noarch
glusterfs-fuse-3.12.2-47.4.el7rhgs.x86_64
glusterfs-geo-replication-3.12.2-47.4.el7rhgs.x86_64
gluster-ansible-features-1.0.5-3.el7rhgs.noarch
glusterfs-client-xlators-3.12.2-47.4.el7rhgs.x86_64
3.cockpit-ovirt-dashboard-0.13.6-1.el7ev


The add brick button is not present during creation of additional volume .
Hence ,moving the bug to verified state.
Comment 3 Sandro Bonazzola 2019-09-26 19:43:05 UTC 
This bugzilla is included in oVirt 4.3.6 release, published on September 26th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.6 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.