Bug 996260 - shutdown -h occasionally reboots, even though init 0 is logged
Summary: shutdown -h occasionally reboots, even though init 0 is logged
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: SysVinit
Version: 5.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-12 19:14 UTC by Allie DeVolder
Modified: 2015-01-02 20:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:08:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Allie DeVolder 2013-08-12 19:14:26 UTC 
Description of problem: shutdown -h occasionally reboots, even though init 0 is logged


Version-Release number of selected component (if applicable):
SysVinit-2.86-15.el5.x86_64

How reproducible:
Unknown

Steps to Reproduce:
1. Configure cron job that runs 'shutdown -h' at a certain time


Actual results:
Perhaps once a month, the system will reboot instead of power down

Expected results:
Consistent power down

Additional info:
This is occurring on a RHEV VM
Comment 1 RHEL Program Management 2014-03-07 12:45:35 UTC 
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Comment 2 RHEL Program Management 2014-06-02 13:08:50 UTC 
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).
Note You need to log in before you can comment on or make changes to this bug.