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 1595646

Summary: The brick configuration in brick tab during deployment is not convenient.
Product: Red Hat Gluster Storage Reporter: Mugdha Soni <musoni>
Component: rhhiAssignee: Sahina Bose <sabose>
Status: CLOSED NOTABUG QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhhiv-1.5CC: rhs-bugs, sankarshan
Target Milestone: ---Keywords: Tracking
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1595648 (view as bug list) Environment:
Last Closed: 2018-10-09 05:39:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1595648    
Bug Blocks:    

Description Mugdha Soni 2018-06-27 09:14:05 UTC
Description of problem:
The configured device name for bricks in host 1 continues to be the device name for the bricks in the other two hosts as well.But if the user changes the brick configuration in host2 or host 1 after a failed deployment or any of such instance it will change in host 3 and in host 2,3 respectively . 

Version-Release number of selected component :

How reproducible

Steps to Reproduce:
1.Log in to the cockpit UI.
2.Start gluster deployment and configure the tabs hosts, packages and volumes.
3.In bricks tab the issue can be seen under brick configuration subtab.

Actual results:
Changes in the brick configuration oH HOST 2 will be reflec

Expected results:
The changes in the device name of host 1 should not reflect in the host 2 and 3

Comment 1 Sahina Bose 2018-10-09 05:39:00 UTC
Closed as per status of tracking bz