Bug 1213125

Summary:	Bricks fail to start with tiering related logs on the brick
Product:	[Community] GlusterFS	Reporter:	Meghana <mmadhusu>
Component:	tiering	Assignee:	Niels de Vos <ndevos>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bugs <bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, dlambrig, josferna, ndevos, skoduri, vagarwal
Target Milestone:	---	Keywords:	Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1215382 (view as bug list)		Environment:
Last Closed:	2016-06-16 12:52:58 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:	1215382, 1260923

Description Meghana 2015-04-19 05:28:33 UTC

Description of problem:
Volume fails to start. 

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


How reproducible:
Always


Steps to Reproduce:
1. Create a volume and attempt to start it.
2.
3.

Actual results:
Volume fails to start. Bricks fail to start on the localhost.

[2015-04-18 17:06:51.310779] I [MSGID: 100030] [glusterfsd.c:2288:main] 0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/glusterfsd version 3.8dev (args: /usr/local/sbin/glusterfsd -s rhs1 --volfile-id testvol.rhs1.tmp-brick1 -p /var/lib/glusterd/vols/testvol/run/rhs1-tmp-brick1.pid -S /var/run/gluster/38b33304ed3bba0bb77e59883a8a91f4.socket --brick-name /tmp/brick1 -l /var/log/glusterfs/bricks/tmp-brick1.log --xlator-option *-posix.glusterd-uuid=3ae0f8b2-ae34-4a7d-b8ea-3afd27e1356c --brick-port 49152 --xlator-option testvol-server.listen-port=49152)
[2015-04-18 17:06:51.329406] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2015-04-18 17:06:51.332254] W [xlator.c:192:xlator_dynload] 0-xlator: /usr/local/lib/glusterfs/3.8dev/xlator/features/changetimerecorder.so: cannot open shared object file: No such file or directory
[2015-04-18 17:06:51.332289] E [graph.y:212:volume_type] 0-parser: Volume 'testvol-changetimerecorder', line 16: type 'features/changetimerecorder' is not valid or not found on this machine
[2015-04-18 17:06:51.332341] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume testvol-changetimerecorder
[2015-04-18 17:06:51.332514] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-04-18 17:06:51.332830] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down
[2015-04-18 17:08:55.145988] I [MSGID: 100030] [glusterfsd.c:2288:main] 0-/usr/local/sbin/glusterfsd: Started running /usr/local/sbin/glusterfsd version 3.8dev (args: /usr/local/sbin/glusterfsd -s 10.70.43.164 --volfile-id testvol.10.70.43.164.tmp-brick1 -p /var/lib/glusterd/vols/testvol/run/10.70.43.164-tmp-brick1.pid -S /var/run/gluster/818424f21d804f3f9c42a0fe0e6c02ed.socket --brick-name /tmp/brick1 -l /var/log/glusterfs/bricks/tmp-brick1.log --xlator-option *-posix.glusterd-uuid=3ae0f8b2-ae34-4a7d-b8ea-3afd27e1356c --brick-port 49153 --xlator-option testvol-server.listen-port=49153)
[2015-04-18 17:08:55.162875] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2015-04-18 17:08:55.165398] W [xlator.c:192:xlator_dynload] 0-xlator: /usr/local/lib/glusterfs/3.8dev/xlator/features/changetimerecorder.so: cannot open shared object file: No such file or directory
[2015-04-18 17:08:55.165455] E [graph.y:212:volume_type] 0-parser: Volume 'testvol-changetimerecorder', line 16: type 'features/changetimerecorder' is not valid or not found on this machine 
[2015-04-18 17:08:55.165530] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume testvol-changetimerecorder
[2015-04-18 17:08:55.165714] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-04-18 17:08:55.166122] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down



Expected results:
Configured gluster with --disable-tiering. Shouldn't have seen these errors.


Additional info:

Comment 1 Anand Avati 2015-04-19 07:44:06 UTC

REVIEW: http://review.gluster.org/10296 (tiering: skip CTR-xlator and config options when disabled) posted (#1) for review on master by Niels de Vos (ndevos)

Comment 2 Anand Avati 2015-04-26 07:11:40 UTC

COMMIT: http://review.gluster.org/10296 committed in master by Vijay Bellur (vbellur) 
------
commit a675ab96b917fc48fc3d7ca035590ebd7cf102bd
Author: Niels de Vos <ndevos>
Date:   Sun Apr 19 09:40:34 2015 +0200

    tiering: skip CTR-xlator and config options when disabled
    
    When compiling with --disable-tiering, GlusterD should not contain any
    references to the ChangeTimeRecorder xlator or any of the data tiering
    options.
    
    BUG: 1213125
    Change-Id: Idb46fb80f0ca8b66115e06841d9ec15ba14c24a0
    Signed-off-by: Niels de Vos <ndevos>
    Reviewed-on: http://review.gluster.org/10296
    Reviewed-by: Dan Lambright <dlambrig>
    Tested-by: Gluster Build System <jenkins.com>

Comment 3 Niels de Vos 2015-05-15 13:07:32 UTC

This change should not be in "ON_QA", the patch posted for this bug is only available in the master branch and not in a release yet. Moving back to MODIFIED until there is an beta release for the next GlusterFS version.

Comment 5 Nagaprasad Sathyanarayana 2015-10-25 14:44:36 UTC

Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.

Comment 6 Niels de Vos 2016-06-16 12:52:58 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report.

glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/
[2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user