Bug 1089620

Summary:	[SNAPSHOT]: Restarting glusterd fails after snapshots are taken on volume
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	senaik
Component:	snapshot	Assignee:	Avra Sengupta <asengupt>
Status:	CLOSED ERRATA	QA Contact:	senaik
Severity:	high	Docs Contact:
Priority:	urgent
Version:	rhgs-3.0	CC:	asengupt, nsathyan, rhinduja, rhs-bugs, ssamanta, storage-qa-internal
Target Milestone:	---	Keywords:	TestBlocker
Target Release:	RHGS 3.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	SNAPSHOT
Fixed In Version:	glusterfs-3.6.0-1.0.el6rhs	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1091833 (view as bug list)		Environment:
Last Closed:	2014-09-22 19:35:53 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:	1091833

Description senaik 2014-04-21 08:00:58 UTC

Description of problem:
======================
After taking snapshots, restarting glusterd fails 


Version-Release number of selected component (if applicable):
============================================================
glusterfs 3.5qa2

How reproducible:
================
always


Steps to Reproduce:
==================
1.Create dist-rep volume and start it 

2.Take few snapshots on the volume 

3.Restart glusterd 

service glusterd restart
Starting glusterd:                                         [FAILED]

Restarting glusterd before taking snapshots works fine.

----------------Part of the Log-----------------------

trieved UUID: 82ebdc84-c429-431f-9eff-f1afbbeb7f0d
[2014-04-21 14:43:57.436827] E [glusterd-store.c:2804:glusterd_resolve_snap_bricks] 0-management: resolve brick failed in restore
[2014-04-21 14:43:57.436881] W [glusterd-store.c:2959:glusterd_store_retrieve_snap] 0-management: resolving the snap bricks failed (snap: snap1)
[2014-04-21 14:43:57.436904] E [glusterd-store.c:3120:glusterd_store_retrieve_snaps] 0-management: Unable to restore snapshot: snap1
[2014-04-21 14:43:57.436935] E [xlator.c:406:xlator_init] 0-management: Initialization of volume 'management' failed, review your volfile again
[2014-04-21 14:43:57.436953] E [graph.c:307:glusterfs_graph_init] 0-management: initializing translator failed
[2014-04-21 14:43:57.436968] E [graph.c:502:glusterfs_graph_activate] 0-graph: init failed
[2014-04-21 14:43:57.437605] W [MSGID: 100032] [glusterfsd.c:1130:cleanup_and_exit] (--> 0-: received signum (0), shutting down


Actual results:
==============
After taking snapshots, restarting glusterd fails


Expected results:
================
Restarting glusterd should work fine before and after taking snapshots

Additional info:

Comment 2 senaik 2014-04-21 09:37:53 UTC

http://rhsqe-repo.lab.eng.blr.redhat.com/bugs_necessary_info/snapshots/1089620/

Comment 3 Avra Sengupta 2014-04-28 07:14:11 UTC

Fix at http://review.gluster.org/#/c/7452/11

Comment 4 Nagaprasad Sathyanarayana 2014-04-28 07:17:51 UTC

Moving to ASSIGNED.  The downstream BZ can be moved to POST once the upstream patch is merged (upstream BZ is moved to MODIFIED).

Comment 5 Rahul Hinduja 2014-05-09 07:07:30 UTC

Verified with build: glusterfs-3.6.0-1.0.el6rhs.x86_64

Able to restart glusterd when snapshots are present in the system.

[root@snapshot09 ~]# service glusterd status
glusterd (pid  18833) is running...
[root@snapshot09 ~]# gluster snapshot list | wc
     10      10      61
[root@snapshot09 ~]# service glusterd restart
Starting glusterd:                                         [  OK  ]
[root@snapshot09 ~]# 


Moving the bug to verified state.

Comment 6 Nagaprasad Sathyanarayana 2014-05-19 10:56:51 UTC

Setting flags required to add BZs to RHS 3.0 Errata

Comment 8 errata-xmlrpc 2014-09-22 19:35:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

http://rhn.redhat.com/errata/RHEA-2014-1278.html