Bug 679812 - initscript's status action should return 3
Summary: initscript's status action should return 3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: edac-utils
Version: 6.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Aristeu Rozanski
QA Contact: Jakub Prokes
URL:
Whiteboard:
Depends On:
Blocks: 579073
TreeView+ depends on / blocked
 
Reported: 2011-02-23 15:01 UTC by Ales Zelinka
Modified: 2014-06-19 08:46 UTC (History)
5 users (show)

Fixed In Version: edac-utils-0.9-15.el6
Doc Type: Bug Fix
Doc Text:
Previously, the exit status of the edac-utils package init script was not set correctly. As a consequence, running the 'service edac status' command returned exit status 0, which was not expected behavior because no programs were running after executing the 'service edac start' command. With this update, the returned exit status has been changed to 3 in the described situation.
Clone Of:
Environment:
Last Closed: 2014-06-19 08:46:00 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:0768 0 normal SHIPPED_LIVE edac-utils bug fix update 2014-06-19 12:45:13 UTC

Description Ales Zelinka 2011-02-23 15:01:15 UTC 
Description of problem:
edac-utils' initscript doesn't control any daemon. There is no program running after 'service edac start' finishes. So it only makes sense for 'service edac status' to exit with exit code 3 = program not running.


Version-Release number of selected component (if applicable):
edac-utils-0.9-12.el6.i686

How reproducible:
always

Steps to Reproduce:
service edac start ; service edac status ; echo $?
  
Actual results:
0

Expected results:
3
Comment 2 RHEL Program Management 2011-07-06 00:21:55 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 3 RHEL Program Management 2013-10-14 01:09:54 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.
Comment 8 Aristeu Rozanski 2014-06-10 17:17:02 UTC 
Sorry, but this was not in the specification of the bug and the fix didn't introduce it, marking it as failed QA is wrong.
Comment 11 errata-xmlrpc 2014-06-19 08:46:00 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-2014-0768.html
Note You need to log in before you can comment on or make changes to this bug.