Bug 251219

Summary: FEAT: RHEL 6.0: Boot-time hang when HPC: 939
Product: Red Hat Enterprise Linux 6 Reporter: Jay Greguske <jay.greguske>
Component: initscriptsAssignee: initscripts Maintenance Team <initscripts-maint-list>
Status: CLOSED NEXTRELEASE QA Contact: Brock Organ <borgan>
Severity: low Docs Contact:
Priority: low    
Version: 6.0CC: jeanne.colon-bonet, karen.skweres, rpacheco, rstrode, tom.wildman
Target Milestone: rcKeywords: Reopened
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-11-12 16:24:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 296431    

Description Jay Greguske 2007-08-07 20:04:14 UTC
Description of problem:
The /etc/rc.sysinit script sets RHGB_STARTED=0 but /etc/init.d/functions checks
if it's null ("").  It caused a problem with headless nodes imaged with
SystemImager software to hang on boot trying to open
/etc/rhgb/temp/rhgb-console.  Removing /etc/rhgb/temp/rhgb-console from the
image solved the problem, but the RHGB_STARTED usage should be fixed to be
consistent.

How reproducible:
Always

Steps to Reproduce:

1. When RHGB is enabled, and it has started, reboot the system. (in the middle
of booting)
2. Remove the "rhgb" parameter in the boot loader entry (in grub or lilo), so
that the system will not start RHGB.
3. Boot the system. You should see it hang when the first initscript is executed.

Comment 1 Ray Strode [halfline] 2007-08-07 20:14:06 UTC
Reassigning to initscripts

Comment 3 Bill Nottingham 2007-09-28 19:51:54 UTC
This problem is fixed in the development tree, and will be resolved in the next
major release of Red Hat Enterprise Linux. Red Hat does not currently plan to
provide a resolution for this in a Red Hat Enterprise Linux update for currently
deployed systems. To get into this situation, you would have to somehow create
an image of a system *while RHGB is running* - the pipe in question is only ever
created on a temporary ramfs filesystem. This is highly unlikely to happen.

With the goal of minimizing risk of change for deployed systems, and in response
to customer and partner requirements, Red Hat takes a conservative approach when
evaluating changes for inclusion in maintenance updates for currently deployed
products. The primary objectives of update releases are to enable new hardware
platform support and to resolve critical defects. 

Comment 4 Daniel Riek 2007-11-09 20:24:22 UTC
As a workaround seems to exist for RHEL 5, moving this to RHEL6 and approving.