Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1597255

Summary: The mount point of the additional volume created during gluster deployment is not correct .
Product: [oVirt] cockpit-ovirt Reporter: Mugdha Soni <musoni>
Component: GdeployAssignee: Parth Dhanjal <dparth>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 0.11.20CC: bugs, rhs-bugs, sabose, sankarshan, sasundar
Target Milestone: ovirt-4.2.6Flags: rule-engine: ovirt-4.2+
rule-engine: devel_ack+
sasundar: testing_ack+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: cockpit-ovirt-0.11.33-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1597253 Environment:
Last Closed: 2018-09-04 06:30:56 UTC Type: Bug
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: 1597253, 1613223    
Attachments:
Description Flags
screenshot of the volume tab.
none
Screenshot of bricks tab in gluster deployment. none

Description Mugdha Soni 2018-07-02 11:51:38 UTC
Created attachment 1455944 [details]
screenshot of the volume tab.

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

Description of problem:
-------------------------------------------
The mount point of the additional volume in gluster deployment is not correct.For eg. if we set the directory of the new volumes as /rhgs/test/test in volume section of deployment ,in the bricks section under mount point it is reflected as rhgs/test/test.This mount point is not correct as the brick should be inside the mount point so the mount point should be rhgs/test.The mount point tab is editable as well which should be seized.

Version-Release number of selected component :
--------------------------------------------
cockpit-ovirt-dashboard-0.11.28-1.el7ev.noarch

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

Steps to Reproduce:
------------------------------------------
1.Log in to the cockpit UI .
2.Start deploying gluster and in volume tabs create an extra volume with the correct brick directory.
3.Under the mount point in brick tab the issue can be found.

Actual results:
-----------------------------------------
The mount point is the same as that of brick directory.


Expected results:
-----------------------------------------
The brick should be inside the mount point .


Additional info:

--- Additional comment from Mugdha Soni on 2018-07-02 07:48 EDT ---

Comment 1 Mugdha Soni 2018-07-02 11:53:14 UTC
Created attachment 1455945 [details]
Screenshot of bricks tab in gluster deployment.

Comment 2 Sahina Bose 2018-07-06 13:36:20 UTC
This seems to be the case when the directory and mountpoint are not the same - for instance in the screenshot provided /gluster_bricks/brick1/b1 and gluster_bricks/data/dataa while /gluster_bricks/vmstore/vmstore has been correctly updated

Comment 3 SATHEESARAN 2018-09-03 18:30:33 UTC
Tested with cockpit-ovirt-0.11.33

Observed when choosing the create new volume with brick dir as '/gluster_bricks/newvol/newvol', the mount point is automatically chosen as '/gluster_bricks/newvol'