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.
Incorrect boot entries were being displayed to the user. This was because incorrect boot entries remained in the grub configuration.This was fixed by removing the incorrect boot entries, so only valid boot entries are shown to the user.
Created attachment 762275[details]
attached Screenshot for boot menu
+++ This bug was initially created as a clone of Bug #868762 +++
Description of problem:
Insert the installation media(CD-ROM/USB), and start the system, When the automatic boot prompt appears, press Enter.
Automatic boot in 30 seconds...
Select the "Boot(Basic Video)" option, and press Enter.
Actually it boot the the Hypervisor installer process, not the Hypervisor
Version-Release number of selected component (if applicable):
rhev-hypervisor6-6.4-20121015.1.el6
How reproducible:
100%
Steps to Reproduce:
1.Insert the installation media(CD-ROM/USB), and start the system.
2.Start the system. When the automatic boot prompt appears, press Enter.
Automatic boot in 30 seconds...
3.Select the "Boot(Basic Video)" option, and press Enter.
Actual result:
After step 3,Boot the Hypervisor installer process, not the the Hypervisor
Expect result:
After step 3,Boot the Hypervisor from CD media in Basic Video mode should be successful.
Additional info:
the difference of "Boot(Basic Video)" and "install(Basic video)":
Boot (Basic Video)
Boot the Hypervisor in Basic Video mode.
Install (Basic Video)
Install the Hypervisor in Basic Video mode.
Test version:
rhev-hypervisor6-6.5-20131017.0.iso
ovirt-node-3.0.1-4.el6
Tested as follows:
1.Insert the installation media(CD-ROM/USB), and start the system.
2.Start the system. When the automatic boot prompt appears, press Enter.
Automatic boot in 30 seconds...
Notice that "Boot(Basic Video)" has been remove from boot option list
so this bug has been fixed, change the status into "VERIFIED"
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-0033.html