Bug 804936

Summary:	service fcoe status gives wrong return value if fcoe service running
Product:	Red Hat Enterprise Linux 6	Reporter:	Miroslav Vadkerti <mvadkert>
Component:	fcoe-utils	Assignee:	Petr Šabata <psabata>
Status:	CLOSED ERRATA	QA Contact:	Petr Beňas <pbenas>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3	CC:	borgan, czhang, fge, pbenas, pstehlik
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	fcoe-utils-1.0.22-3.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-20 13:50:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Miroslav Vadkerti 2012-03-20 09:00:39 UTC

Description of problem:
# service fcoe restart
Stopping FCoE initiator service:                           [  OK  ]
Starting FCoE initiator service:                           [  OK  ]

# service fcoe status
/usr/sbin/fcoemon is running, pid=29187
No interfaces created.

# echo $?
2

Version-Release number of selected component (if applicable):
fcoe-utils-1.0.22-1.el6

How reproducible:
100%

Steps to Reproduce:
see description
  
Actual results:
status return 2
2:	program is dead and /var/lock lock file exists

Expected results:
status return 0

Additional info:
This is a regression as this bug cannot be reproduced with fcoe-utils-1.0.20-5.el6

Comment 3 Petr Šabata 2012-03-22 15:23:45 UTC

Good catch.  This was changed intentionally upstream (d789267) but apparently isn't in line with our guidelines.

Comment 7 Petr Šabata 2012-03-30 08:06:31 UTC

Any update?

Comment 14 Petr Beňas 2012-04-03 12:18:57 UTC

Reproduced in fcoe-utils-1.0.22-1.el6.x86_64 and verified in fcoe-utils-1.0.22-2.el6.x86_64.

Comment 16 errata-xmlrpc 2012-06-20 13:50:27 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.

http://rhn.redhat.com/errata/RHBA-2012-0851.html