RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 613031 - initscript: guideline compliance
Summary: initscript: guideline compliance
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: openwsman
Version: 6.0
Hardware: All
OS: Linux
high
medium
Target Milestone: rc
: ---
Assignee: Vitezslav Crhonek
QA Contact: Martin Cermak
URL:
Whiteboard:
Depends On:
Blocks: 633349
TreeView+ depends on / blocked
 
Reported: 2010-07-09 14:55 UTC by Ales Zelinka
Modified: 2011-05-19 13:04 UTC (History)
4 users (show)

Fixed In Version: openwsman-2.2.3-8.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-05-19 13:04:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
RHBA-2011-10472 testing results (16.42 KB, application/x-gzip)
2011-03-15 09:04 UTC, Martin Cermak 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:0563 0 normal SHIPPED_LIVE openwsman bugfix update 2011-05-18 17:57:12 UTC

Description Ales Zelinka 2010-07-09 14:55:16 UTC 
Description of problem:
There's few issues with the openwsman's initscript:

According to these guidelines
https://fedoraproject.org/wiki/Packaging/SysVInitScript

The initscript should:

1) return 3 when status of a stopped service is queried:
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: Stop
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: Running 'service openwsmand stop'
:: [   FAIL   ] :: Running 'service openwsmand status' (Expected 3, got 0)
:: [   PASS   ] :: Running 'service openwsmand stop'
:: [   FAIL   ] :: Running 'service openwsmand status' (Expected 3, got 0)


2)PID file:
openwsmand creates pidfile /var/run/wsmand.pid instead of /var/run/openwsmand.pid as defined in the initscript. That itself is not an issue, but might help explain why: the pidfile is not removed when service is stopped.

3) exit code should be 2 when an invalid argument is provided:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: Invalid arguments
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   FAIL   ] :: Running 'service openwsmand' (Expected 2, got 0)



Version-Release number of selected component (if applicable):
openwsman-server-2.2.3-5.el6.i686
Comment 13 Martin Cermak 2011-03-15 09:08:20 UTC 
Verified manually on stable systems. See testing results [1] above. 

[1] https://bugzilla.redhat.com/show_bug.cgi?id=613031#c12
Comment 14 errata-xmlrpc 2011-05-19 13:04:22 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0563.html
Note You need to log in before you can comment on or make changes to this bug.