Bug 1325750

Summary:	Volume stop is failing when one of brick is down due to underlying filesystem crash
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Byreddy <bsrirama>
Component:	glusterd	Assignee:	Atin Mukherjee <amukherj>
Status:	CLOSED ERRATA	QA Contact:	Byreddy <bsrirama>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	mchangir, rcyriac, rhinduja, rhs-bugs, storage-qa-internal, vbellur
Target Milestone:	---	Keywords:	Regression, ZStream
Target Release:	RHGS 3.1.3
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	glusterfs-3.7.9-2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1325841 (view as bug list)		Environment:
Last Closed:	2016-06-23 05:16:28 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:	1311817, 1325841, 1326174

Description Byreddy 2016-04-11 05:46:24 UTC

Description of problem:
=======================
When one of brick is down due to underlying filesystem (here xfs) crash, volume stop is failing with error message "volume stop: Dis: failed: brick operations failed"


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.9-1

How reproducible:
=================
Always


Steps to Reproduce:
===================
1. Have one node cluster
2. Create 1*2 volume and start it.
3. crash underlying filesystem for one of the volume brick using "godown tool"
4. Check brick is down using "volume status"
5. Try to stop the volume // it will fail.


Actual results:
===============
Volume stop is failing with error message "volume stop: Dis: failed: brick operations failed"

Expected results:
=================
Volume stop should work properly.


Additional info:
================

Comment 3 Milind Changire 2016-04-11 10:45:11 UTC

Providing devel_ack+ since BZ has been categorized as Regression.

Comment 4 Atin Mukherjee 2016-04-11 10:48:35 UTC

I've the RCA now and the commit message of http://review.gluster.org/#/c/13965 explains it. Since the upstream patch is posted for review moving the status to Post.

Comment 5 Atin Mukherjee 2016-04-12 04:06:54 UTC

3.7 patch : http://review.gluster.org/#/c/13973 posted for review.

Comment 6 Atin Mukherjee 2016-04-18 14:21:23 UTC

Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/71623/

Comment 8 Atin Mukherjee 2016-04-18 14:22:28 UTC

(In reply to Atin Mukherjee from comment #6)
> Downstream patch : https://code.engineering.redhat.com/gerrit/#/c/71623/

This is a wrong link, ignore. Correct link is https://code.engineering.redhat.com/gerrit/#/c/72433/

Comment 9 Atin Mukherjee 2016-04-18 14:23:36 UTC

Downstream patch is merged now.

Comment 11 Byreddy 2016-04-25 08:17:19 UTC

Verified this bug using the build "glusterfs-3.7.9-2.el7rhgs".

Repeated the steps specified in description section.


Fix is working good, moving to verified state.

Comment 13 errata-xmlrpc 2016-06-23 05:16:28 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.

https://access.redhat.com/errata/RHBA-2016:1240