Bug 958079

Summary:	glusterd: response not aligned
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Saurabh <saujain>
Component:	core	Assignee:	Bug Updates Notification Mailing List <rhs-bugs>
Status:	CLOSED NOTABUG	QA Contact:	SATHEESARAN <sasundar>
Severity:	high	Docs Contact:
Priority:	medium
Version:	2.1	CC:	mzywusko, rhs-bugs, sasundar, storage-qa-internal, vagarwal, vbellur
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	glusterd
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1211845 (view as bug list)		Environment:
Last Closed:	2015-04-15 05:37:37 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:	1321762, 1322667
Bug Blocks:	1211845

Description Saurabh 2013-04-30 10:44:30 UTC

Description of problem:

response string for /etc/init.d/glusterd is not aligned
Version-Release number of selected component (if applicable):
glusterfs-3.4.0.1rhs-1.el6rhs.x86_64

How reproducible:
on all my rhs nodes

Steps to Reproduce:
1.
/etc/init.d/glusterd stop
  
Actual results:
[root@rhs-goldman2 ~]# /etc/init.d/glusterd stop
[root@rhs-goldman2 ~]#                                     [  OK  ]


Expected results:
it should be similar to,
[root@rhs-goldman2 ~]# /etc/init.d/glusterd start
Starting glusterd:                                         [  OK  ]


Additional info:

Comment 2 Amar Tumballi 2013-05-03 05:56:33 UTC

looks like a minor fix required in glusterd init script. good to target fixing, as its a cosmetic issue for admins.

Comment 4 SATHEESARAN 2014-05-14 08:55:52 UTC

The issue is still seen with RHS 3.0 Nightly builds ( glusterfs-3.6.0-4.0.el6rhs )

[root@rhss1 ~]# service glusterd stop
[root@rhss1 ~]# d:                                         [  OK  ]

Comment 5 SATHEESARAN 2014-12-03 09:42:08 UTC

This issue is no longer seen in RHS 2.1 U* bits. But the issue is seen with RHS 3.0 Bits. I feel this bug could be closed wrt RHS 2.1

Comment 10 SATHEESARAN 2015-04-15 05:37:37 UTC

This bug is raised for RHS 2.1.x

But this problem is no longer reproducible in RHS 2.1.x and so I am closing this bug as NOTABUG and cloned this bug for RH-Gluster Storage 3.0
https://bugzilla.redhat.com/show_bug.cgi?id=1211845