Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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:

When I provision a machine in beaker with nightly RHEL6 and I boot-up, I do not see a login gialog on tty1. That's because default runlevel is set to 5 although no Xs are present. It results in long line (boot line) drawn and no keyboard response on tty1 which feels at least weird.

Version-Release number of selected component (if applicable):
RHEL6.0-20100713.n.1_nfs-Server-x86_64

How reproducible:
always

Steps to Reproduce:
1. provision a machine (I tried intel-d3ca2-01.lab.bos.redhat.com) using beaker.
2. boot and run "runlevel"
  
Actual results:
N 5

Expected results:
N 3

Please attach /var/log/anaconda.log and /root/install.log from the installed system to this bug report.

Created attachment 431800 [details]
anaconda.log

Created attachment 431801 [details]
install.log

This issue has been proposed when we are only considering blocker
issues in the current Red Hat Enterprise Linux release. It has
been denied for the current Red Hat Enterprise Linux release.

** If you would still like this issue considered for the current
release, ask your support representative to file as a blocker on
your behalf. Otherwise ask that it be considered for the next
Red Hat Enterprise Linux release. **

Your kickstart file specifies that X should be started:

# Configure the X Window System
xconfig --startxonboot