Bug 1278765

Summary:	[Tier]: Volume/GlusterD start is not starting the not running bricks (killed bricks)
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Byreddy <bsrirama>
Component:	tier	Assignee:	Gaurav Kumar Garg <ggarg>
Status:	CLOSED NOTABUG	QA Contact:	Nag Pavan Chilakam <nchilaka>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.1	CC:	amukherj, asrivast, bsrirama, rhs-bugs, smohan, storage-qa-internal, vagarwal
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.1.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-20 06:36:39 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:	1260923

Description Byreddy 2015-11-06 11:25:37 UTC

Description of problem:
======================
Force volume start /glusterd restart is not starting the not running bricks (killed bricks). 


Version-Release number of selected component (if applicable):
=============================================================
glusterfs-3.7.5-5


How reproducible:
==================
100%


Steps to Reproduce:
===================
1.Create a tiered volume 
2. kill one of the brick in the volume
3.force start the volume (gluster volume start force) OR restart the glusterd
4. Check the killed brick in step-2 is up. 

Actual results:
===============
Force Volume start is not bringing the killed brick up


Expected results:
=================
Force Volume should brick back the killed bricks up.


Additional info:
=================
This is working well with normal volume (with out tiering )

Comment 3 Gaurav Kumar Garg 2015-11-19 12:10:50 UTC

It seems this bug already fixed by someone else. this bug is not reproducible in latest build. This bug will be close once we will found the patch of this bug.

Comment 4 Gaurav Kumar Garg 2015-11-19 12:20:43 UTC

Byreddy could you update this bug with sos report or log file once you able to reproduce it. or If it is not able to reproduce then we need to find out which patch fixed this bug according to that we will close this bug.

Comment 5 Byreddy 2015-11-20 06:36:39 UTC

(In reply to Gaurav Kumar Garg from comment #4)
> Byreddy could you update this bug with sos report or log file once you able
> to reproduce it. or If it is not able to reproduce then we need to find out
> which patch fixed this bug according to that we will close this bug.

This issue is not reproducing with old build ( glusterfs-3.7.5-5 ) and with latest build (glusterfs-3.7.5-6) also.It's working properly without any issue, so closing this bug.