Bug 522806 - fcoe-utils initscript is not LSB compliant
Summary: fcoe-utils initscript is not LSB compliant
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: fcoe-utils
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Jan Zeleny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: InitScriptsProject
TreeView+ depends on / blocked
 
Reported: 2009-09-11 14:46 UTC by Miroslav Vadkerti
Modified: 2009-09-14 15:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 536894 (view as bug list)
Environment:
Last Closed: 2009-09-14 14:50:27 UTC


Attachments (Terms of Use)

Description Miroslav Vadkerti 2009-09-11 14:46:36 UTC
Description of problem:
According to https://fedoraproject.org/wiki/FCNewInit/Initscripts there are
several issues with fcoe-utils initscript:

PROBLEM 1:
Status after amtu is stopped returns 1, should be 3

PROBLEM 2:
Status after amtu is not running but lock file exists returns 0, should be 2

PROBLEM 3:
Status after amtu is not running but pid file exists returns 0, should be 1

Version-Release number of selected component (if applicable):
fcoe-utils-1.0.8-2.fc12

How reproducible:
always

Steps to Reproduce:
PROBLEM 1:
 1. service fcoe stop
 2. service fcoe status; echo $?
  
 Actual results:
 1

 Expected results:
 3

PROBLEM 2:
 1. touch /var/lock/subsys/fcoe
 2. service fcoe status; echo $?
  
 Actual results:
 0

 Expected results:
 2

PROBLEM 3:
 1. touch /var/run/fcoe.pid
 2. service fcoe status; echo $?
  
 Actual results:
 0

 Expected results:
 1

Comment 1 Miroslav Vadkerti 2009-09-11 16:34:53 UTC
CORRECTION:

In the bug report please s/amtu/fcoe

Comment 2 Jan Zeleny 2009-09-14 10:53:53 UTC
The issue has been fixed, new build is available.

Comment 3 Miroslav Vadkerti 2009-09-14 13:59:28 UTC
Bug reopned as the pid file issue 3 still isn't fixed:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: PID file
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   PASS   ] :: Running 'touch /var/run/fcoe.pid'
:: [   FAIL   ] :: Running 'service fcoe status' (Expected 1, got 2)
:: [   LOG    ] :: Duration: 1s
:: [   LOG    ] :: Assertions: 1 good, 1 bad
:: [   FAIL   ] :: RESULT: PID file

Comment 4 Jan Zeleny 2009-09-14 14:50:11 UTC
After a consultation the source of issue has been discovered. Closing again.


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