Bug 1721028

Summary:	gluster v heal <vol_name> info is stuck
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Upasana <ubansal>
Component:	disperse	Assignee:	Ashish Pandey <aspandey>
Status:	CLOSED ERRATA	QA Contact:	Upasana <ubansal>
Severity:	high	Docs Contact:
Priority:	low
Version:	rhgs-3.5	CC:	amukherj, aspandey, nchilaka, rhs-bugs, rkavunga, storage-qa-internal, vdas
Target Milestone:	---	Keywords:	Regression
Target Release:	RHGS 3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-6.0-7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 12:21:54 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:	1696809

Description Upasana 2019-06-17 07:36:35 UTC

Description of problem:
========================
gluster v heal <vol_name> info is stuck from the past 3 hours

Version-Release number of selected component (if applicable):
=============================================================
glusterfs-6.0-5.el7rhgs.x86_64

How reproducible:
================
1/1


Steps to Reproduce:
====================

Was trying to verify Bug 1716385 - [EC] volume heal info command stucks forever even if all bricks are running  and had created 10000 files and 10 directories
1.Created a 3X(4+2) EC volume 
2.Brought down 2 bricks from each subvol 
3.Created 10000 files and 10 directories
4.Started volume - Force
5.Gave gluster v heal <vol_name> info


Actual results:
===============
Heal info is hanging

Expected results:
=================
Heal info is hanging

Additional info:
================
Had done the exact same steps on a 3.4.4 setup and everything is fine there , even healing has completed


The setup is in the same state if anyone wants to debug , will ping the details.

Comment 15 Atin Mukherjee 2019-06-24 07:09:38 UTC

This looks to be a blocker. I am acking this bug right away, investigation can continue.

Comment 22 errata-xmlrpc 2019-10-30 12:21:54 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/RHEA-2019:3249