Bug 804936 - service fcoe status gives wrong return value if fcoe service running
Summary: service fcoe status gives wrong return value if fcoe service running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: fcoe-utils
Version: 6.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Petr Šabata
QA Contact: Petr Beňas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 09:00 UTC by Miroslav Vadkerti
Modified: 2015-01-04 23:02 UTC (History)
5 users (show)

Fixed In Version: fcoe-utils-1.0.22-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-20 13:50:27 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:0851 0 normal SHIPPED_LIVE fcoe-utils bug fix and enhancement update 2012-06-19 20:48:37 UTC

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


Note You need to log in before you can comment on or make changes to this bug.