Bug 724954

Summary: stop target from init script misbehaves
Product: Red Hat Enterprise Linux 6 Reporter: Michal Nowak <mnowak>
Component: opensshAssignee: Jan F. Chadima <jchadima>
Status: CLOSED NEXTRELEASE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: mvadkert, ohudlick, pvrabec
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-27 12:42:18 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 Michal Nowak 2011-07-22 12:23:45 UTC
Description of problem:

Start sshd service and then stop it:

[newman@dhcp-25-35 ~]$ sudo service sshd start
Starting sshd:                                             [  OK  ]
[newman@dhcp-25-35 ~]$ sudo service sshd stop
Stopping sshd: Stopping sshd:                              [FAILED]

Return code == 1.

I verified sshd process was running after start() and is not running after stop().

Version-Release number of selected component (if applicable):

openssh-5.3p1-62.el6.x86_64

How reproducible:

always

I'd expect stop() to return 1 when it actually terminates sshd process.

Comment 2 Michal Nowak 2011-07-25 10:00:24 UTC
Well, I wanted this bug to be fixed in RHEL6 because it makes my test to fail. Can you be more verbose on why this bug should by closed from your point of view?

Comment 3 Jan F. Chadima 2011-07-25 10:50:56 UTC
sorry

Comment 4 Miroslav Vadkerti 2011-07-26 14:39:10 UTC
This bug may be caused by the fix of
https://bugzilla.redhat.com/show_bug.cgi?id=698777
which is not a bug really and will be removed from the next build. 
If this test case passes with latest released
openssh-5.3p1-52.el6_1.2 package this request should be closed as not a bug or something like that. Of course we can wait for next build and retest.

Comment 5 Miroslav Vadkerti 2011-07-26 15:20:29 UTC
According to the reporter this bug is not reproducable with openssh-5.3p1-52.el6_1.2. We will retest with the latest openssh when it gets build to be sure though.

Comment 6 Jan F. Chadima 2011-07-27 12:42:18 UTC
This bug is repaired by unrolling the init script change.