Bug 1220381

Summary:	unable to start the volume with the latest beta1 rpms
Product:	[Community] GlusterFS	Reporter:	Gaurav Kumar Garg <ggarg>
Component:	build	Assignee:	Satish Mohan <smohan>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs, ndevos, sasundar, sgraf, smohan
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.8rc2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1220338	Environment:
Last Closed:	2016-06-16 13:00:02 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:	1186580, 1220338

Description Gaurav Kumar Garg 2015-05-11 12:56:08 UTC

+++ This bug was initially created as a clone of Bug #1220338 +++

Description of problem:
-----------------------
Starting the volume failed with error message "volume start: rvstore: failed: Commit failed on localhost. Please check the log file for more details."

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
glusterfs-3.7.0beta1-0.155.git72f80ae.el6.x86_64

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Create any type of volume
2. Start the volume

Actual results:
---------------
Volume start failed with error message - "volume start: rvstore: failed: Commit failed on localhost. Please check the log file for more details."

Expected results:
-----------------
The volume should get started


Additional info:
----------------
From the brick logs, - marker.so shared object is not available
<brick_log>
[2015-05-11 16:18:45.696874] I [event-epoll.c:629:event_dispatch_epoll_worker] 0-epoll: Started thread with index 1
[2015-05-11 16:18:45.704971] W [xlator.c:192:xlator_dynload] 0-xlator: /usr/lib64/glusterfs/3.7.0beta1/xlator/features/marker.so: cannot open shared object file: No such file or directory
[2015-05-11 16:18:45.705013] E [graph.y:212:volume_type] 0-parser: Volume 'rvstore-marker', line 78: type 'features/marker' is not valid or not found on this machine
[2015-05-11 16:18:45.705056] E [graph.y:321:volume_end] 0-parser: "type" not specified for volume rvstore-marker
[2015-05-11 16:18:45.705447] E [MSGID: 100026] [glusterfsd.c:2142:glusterfs_process_volfp] 0-: failed to construct the graph
[2015-05-11 16:18:45.705776] W [glusterfsd.c:1212:cleanup_and_exit] (--> 0-: received signum (0), shutting down
</brick_log>

--- Additional comment from SATHEESARAN on 2015-05-11 07:23:56 EDT ---

Gaurav helped in reproducing the same with the MASTER and there he is not facing the problem. We could conclude that this could be the problem with packaging in that case. 

Probably marker.so is not provided as expected.

--- Additional comment from Stanislav Graf on 2015-05-11 07:35:57 EDT ---

Comment 1 Anand Avati 2015-05-11 12:57:12 UTC

REVIEW: http://review.gluster.org/10752 (rpm: makrer xlator should part of server package) posted (#1) for review on master by Gaurav Kumar Garg (ggarg)

Comment 2 Anand Avati 2015-05-11 12:57:54 UTC

REVIEW: http://review.gluster.org/10752 (build: makrer xlator should part of server package) posted (#2) for review on master by Gaurav Kumar Garg (ggarg)

Comment 3 Anand Avati 2015-05-11 12:58:38 UTC

REVIEW: http://review.gluster.org/10753 (build: makrer xlator should part of server package) posted (#1) for review on release-3.7 by Gaurav Kumar Garg (ggarg)

Comment 4 Anand Avati 2015-05-11 13:38:21 UTC

REVIEW: http://review.gluster.org/10752 (rpm: marker xlator should part of the server sub-package) posted (#3) for review on master by Niels de Vos (ndevos)

Comment 5 Gaurav Kumar Garg 2016-02-14 14:36:17 UTC

change I77fe8a have been merged. moving status of the bug as a modified.

Comment 8 Niels de Vos 2016-06-16 13:00:02 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