Bug 796235

Summary: vmhost does not delete PID file in/var/run
Product: Red Hat Enterprise Linux 6 Reporter: Ralf Thelen <ralf.thelen>
Component: vhostmdAssignee: Richard W.M. Jones <rjones>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1CC: lagarcia, leiwang, moli, qguan, qwan
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-24 11:54:20 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 Ralf Thelen 2012-02-22 14:40:52 UTC
Description of problem:
vhostmd-0.4-2.el5_3
While doing some RAS test cases I noticed a wrong behaviour of the vhostmd
startup script '/etc/init.d/vhostmd'.

# kill -11 vhostmd
# service vhostmd status
vhostmd dead but pid file exists
# service vhostmd stop
# service vhostmd start
Starting vhostmd:                                          [  OK  ]
# service vhostmd status
vhostmd dead but subsys locked

I noticed that the ' /etc/init.d/vhostmd' stop() function has logic to remove
the PID file in /var/run/.
However it is not executed during stop action, because an addtional status
check is done.

stop)
        rh_status_q || exit 0
        $1
        ;;

We have RAS logic that relies on the correct behaviour of the service startup
scripts.


Version-Release number of selected component (if applicable):vhostmd-0.4-2.el5_3

How reproducible:
start vmhost

Steps to Reproduce:
1.
2.
3.
  
Actual results:
see above


Expected results:
vmhost should delet PID file in /var/run/

Additional info:
IBM Tester: thomas.weber.com
IBM Project Manager: ralf.thelen.com (opening this bug)

We think, we know what needs to be done in vhostmd. If you need this technical information let Ralf Thelen (know).

Comment 2 Ralf Thelen 2012-02-23 11:46:17 UTC
We need a fix till 20th March 2012.

Comment 3 Ralf Thelen 2012-02-24 11:54:59 UTC
I will open same bug again with another IBM process (including mirrowing).

Comment 4 Richard W.M. Jones 2012-04-01 19:41:00 UTC
I think the close status was wrong.  This seems to
be a duplicate of bug 766674.

*** This bug has been marked as a duplicate of bug 766674 ***