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 1595648 - The brick configuration in brick tab during deployment is not convenient.
Summary: The brick configuration in brick tab during deployment is not convenient.
Alias: None
Product: cockpit-ovirt
Classification: oVirt
Component: Gdeploy
Version: 0.11.20
Hardware: x86_64
OS: Linux
Target Milestone: ovirt-4.2.7
: ---
Assignee: Parth Dhanjal
Depends On:
Blocks: 1595646
TreeView+ depends on / blocked
Reported: 2018-06-27 09:16 UTC by Mugdha Soni
Modified: 2018-09-05 12:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1595646
Last Closed: 2018-09-05 12:00:38 UTC
oVirt Team: Gluster
rule-engine: ovirt-4.2?
musoni: planning_ack?
musoni: devel_ack?
musoni: testing_ack?

Attachments (Terms of Use)

Description Mugdha Soni 2018-06-27 09:16:19 UTC
+++ This bug was initially created as a clone of Bug #1595646 +++

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-09-05 12:00:38 UTC
This is the way the UI has been designed to avoid multiple inputs from user

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