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

Bug 1719332

Summary:	Change default gluster mount point to /gluster_bricks
Product:	[oVirt] ovirt-engine	Reporter:	Gobinda Das <godas>
Component:	BLL.Gluster	Assignee:	Gobinda Das <godas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	high
Version:	future	CC:	bugs, jcall
Target Milestone:	ovirt-4.3.5	Flags:	pm-rhel: ovirt-4.3+ godas: devel_ack+ sasundar: testing_ack+
Target Release:	4.3.5.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.5.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1823712 (view as bug list)		Environment:
Last Closed:	2019-07-30 14:08:09 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:	1712735, 1823712

Description Gobinda Das 2019-06-11 14:16:20 UTC

Description of problem:
 Currently cockpit is default setting gluster brick mount point to /gluster_bricks but engine is setting to /gluster-bricks, which is misleading.
 

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


How reproducible:
Go to create brick in engine UI and give brick name, the default mount point will come as /gluster-bricks

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:
 Engine also should set default mount point as /gluster_bricks

Additional info:

Comment 1 SATHEESARAN 2019-07-18 07:20:25 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 2 Sandro Bonazzola 2019-07-30 14:08:09 UTC

This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.5 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.