Bug 1210182 - Brick start fails, if source is compiled with disable-tiering.
Summary: Brick start fails, if source is compiled with disable-tiering.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: GlusterFS
Classification: Community
Component: tiering
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact: bugs@gluster.org
URL:
Whiteboard:
Depends On:
Blocks: 1260923
TreeView+ depends on / blocked
 
Reported: 2015-04-09 06:50 UTC by Avra Sengupta
Modified: 2015-10-30 17:32 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-18 22:25:44 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.