Bug 1726901

Summary:	get-state does not show correct brick status
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Mohit Agrawal <moagrawa>
Component:	glusterd	Assignee:	Mohit Agrawal <moagrawa>
Status:	CLOSED DUPLICATE	QA Contact:	Bala Konda Reddy M <bmekala>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.5	CC:	amukherj, nchilaka, rhs-bugs, sankarshan, storage-qa-internal, vbellur
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1726905 1726906 (view as bug list)		Environment:
Last Closed:	2019-07-08 03:04: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:	1726905, 1726906, 1726991

Description Mohit Agrawal 2019-07-04 03:59:15 UTC

Description of problem:

get-state does not show correct brick status
Version-Release number of selected component (if applicable):


How reproducible:

glusterd maintains 4 brick status (GF_BRICK(STARTING|STOPPING|STARTED|STOPPED) but get-status shows only 2 states (Stopped/Started) even in case of STARTING/STOPPING also it shows brick status started which is not correct.

Steps to Reproduce:
1.Not easy to reproduce
2.
3.

Actual results:
get-state is not showing correct brick status

Expected results:
get-status should show correct brick status

Additional info:

Comment 3 Atin Mukherjee 2019-07-08 03:04:39 UTC


*** This bug has been marked as a duplicate of bug 1726991 ***