Description of problem: when user tries to create a brick default mount point as of now in the UI is /gluster-bricks/brick where as it should be /rhgs/brick Version-Release number of selected component (if applicable): rhevm-3.6.3.3-0.1.el6.noarch How reproducible: Always Steps to Reproduce: 1. Login to UI 2. Try creating a brick from UI 3. Actual results: By default the mount point is chosen as /gluster-bricks/<brickname> Expected results: By default the mount point should be /rhgs/<brickname> Additional info:
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
RHGS downstream documentation and tools continue to refer to mount point as /rhgs - hence need this downstream change to be consistent with these tools and documentation. Retargeting to 3.6.6 as this is a minor change.
(In reply to Sahina Bose from comment #6) > RHGS downstream documentation and tools continue to refer to mount point as > /rhgs - hence need this downstream change to be consistent with these tools > and documentation. > > Retargeting to 3.6.6 as this is a minor change. Sahina are you sure this should go to rhevm-setup-plugins and not to rhsc-setup-plugins? Why is this becoming an issue in 3.6.6? Has documentation and tools changed since 3.5? Why /rhgs is now required and it wasn't before?
(In reply to Sandro Bonazzola from comment #7) > (In reply to Sahina Bose from comment #6) > > RHGS downstream documentation and tools continue to refer to mount point as > > /rhgs - hence need this downstream change to be consistent with these tools > > and documentation. > > > > Retargeting to 3.6.6 as this is a minor change. > > Sahina are you sure this should go to rhevm-setup-plugins and not to > rhsc-setup-plugins? > > Why is this becoming an issue in 3.6.6? > Has documentation and tools changed since 3.5? > > Why /rhgs is now required and it wasn't before? Yes, this is for rhevm-setup-plugins to change the downstream rhev behaviour. (rhsc has a separate d/s change) It is targeted for 3.6.6 as we want HC setup to work with minimal user changes. Brick provisioning was not available in 3.5
(In reply to Sahina Bose from comment #8) > Yes, this is for rhevm-setup-plugins to change the downstream rhev > behaviour. (rhsc has a separate d/s change) I see https://gerrit.ovirt.org/#/c/55048/ is meant to fix the issue upstream, if so why do you need to change rhevm-setup-plugins?
(In reply to Sandro Bonazzola from comment #9) > (In reply to Sahina Bose from comment #8) > > Yes, this is for rhevm-setup-plugins to change the downstream rhev > > behaviour. (rhsc has a separate d/s change) > > I see https://gerrit.ovirt.org/#/c/55048/ is meant to fix the issue > upstream, if so why do you need to change rhevm-setup-plugins? I submitted this upstream patch initially - but it wasn't the right approach as it's a downstream specific name. Hence the change to rhevm-setup-plugins and change of product in bz. Abandoning the upstream patch in favour of rhevm-setup-plugin change
Tested with gluster 3.7.9 and RHV 4.0.2-6 The bricks are mounted at /rhgs/<given-brick-name>
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-1675.html