RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

Reassigning to initscripts

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. 

As a workaround seems to exist for RHEL 5, moving this to RHEL6 and approving.