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

Bug 1210182

Summary:	Brick start fails, if source is compiled with disable-tiering.
Product:	[Community] GlusterFS	Reporter:	Avra Sengupta <asengupt>
Component:	tiering	Assignee:	Mohammed Rafi KC <rkavunga>
Status:	CLOSED NOTABUG	QA Contact:	bugs <bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, dlambrig, nchilaka, rkavunga, vagarwal
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-18 22:25:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1260923

Description Avra Sengupta 2015-04-09 06:50:32 UTC

Description of problem:
When installing from upstream source, if disable-tiering option is given during configure, and the vm doesn't have sqlite installed, then bricks fail to start owing to the absence of a shared object.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Anand Avati 2015-04-18 21:31:16 UTC

REVIEW: http://review.gluster.org/10294 (tiering: Add CTR xlator only if tiering is enabled) posted (#1) for review on master by mohammed rafi  kc (rkavunga)

Comment 2 Dan Lambright 2015-04-18 21:59:48 UTC

This is not a bug, the user should install sqlite. If they cannot install sqlite they can disable tiering with a configuration switch.