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 ---
Created attachment 1455945 [details] Screenshot of bricks tab in gluster deployment.
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
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'