Bug 1712735 - Revert fix for bug 1311895 as the brick path mismatch
Summary: Revert fix for bug 1311895 as the brick path mismatch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhvm-setup-plugins
Version: 4.3.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.3.5
: 4.3.5
Assignee: Gobinda Das
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On: 1719332 1823712
Blocks: 1719212 1723792
TreeView+ depends on / blocked
 
Reported: 2019-05-22 07:17 UTC by Gobinda Das
Modified: 2020-04-14 10:33 UTC (History)
3 users (show)

Fixed In Version: rhvm-setup-plugins-4.3.3-1.el7ev
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1719212 (view as bug list)
Environment:
Last Closed: 2019-08-12 11:54:51 UTC
oVirt Team: Gluster
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:2438 0 None None None 2019-08-12 11:54:57 UTC

Description Gobinda Das 2019-05-22 07:17:36 UTC 
Description of problem:
RHHI installer deploy Gluster bricks at "/gluster_bricks" while the hosted-engine is configured to look for bricks at "/rhgs" which causes issue.

Version-Release number of selected component (if applicable):


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 /rhgs/<brickname>

Expected results:
By default the mount point should be /gluster-bricks/<brickname>

Additional info:
Comment 4 SATHEESARAN 2019-07-18 07:21:15 UTC 
Verified with 4.3.5.4 and RHGS 3.4.4 async ( glusterfs-3.12.2-47.2 )

When new bricks are created from RHV Manager UI, the bricks are mounted
at /gluster_bricks/<dir> instead of /rhgs/<dir>
Comment 6 errata-xmlrpc 2019-08-12 11:54:51 UTC 
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://access.redhat.com/errata/RHBA-2019:2438
Note You need to log in before you can comment on or make changes to this bug.