Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
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.
Bug 592080 - GRUB bootloader should have a few seconds delay on a multi-boot setup
Summary: GRUB bootloader should have a few seconds delay on a multi-boot setup
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Release Test Team
URL:
Whiteboard:
: 592060 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-13 19:51 UTC by Bill Nottingham
Modified: 2014-03-17 03:23 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 590661
Environment:
Last Closed: 2010-05-17 09:35:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Bill Nottingham 2010-05-13 19:51:45 UTC 
+++ This bug was initially created as a clone of Bug #590661 +++

Description of problem:


GRUB by default in configured in Fedora to not show the menu and have zero delay but in a multi-boot environment where Anaconda detects Windows and configures GRUB to boot Windows as a alternative, GRUB was configured by Anaconda to have a few seconds delay and show the menu so that the user can choose between Fedora and Windows. 

Unfortunately this is not the case with Fedora 13 RC2 anymore.  This results in a non-technical user unable to boot into Windows after installing Fedora 13.  I am marking it as a blocker

--- Additional comment from awilliam on 2010-05-10 10:38:40 EDT ---

Can anyone confirm how this behaved in F12?

--- Additional comment from metherid on 2010-05-10 14:17:15 EDT ---

Fedora 12 works as expected.  This is a regression.

--- Additional comment from leigh123linux on 2010-05-11 05:05:44 EDT ---

This never worked in F12 for me (I multi-boot several Linux distro's).


https://bugzilla.redhat.com/show_bug.cgi?id=541315

The zero delay sucks.

--- Additional comment from leigh123linux on 2010-05-11 05:06:14 EDT ---

(In reply to comment #3)
> This never worked in F12 for me (I multi-boot several Linux distro's).
> 
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=541315
> 
> The zero delay sucks.    

And it still doesn't work in F13.

--- Additional comment from pjones on 2010-05-11 09:45:56 EDT ---

*** Bug 574994 has been marked as a duplicate of this bug. ***

--- Additional comment from narfman0 on 2010-05-11 09:49:39 EDT ---

Worked for me F12 on 2/2 of my machines as Rahul explains. 0 delay does suck..!

--- Additional comment from poelstra on 2010-05-11 21:02:14 EDT ---

Reviewed by a QA, Release Engineering, etc. at 2010-05-11 "Go/No-Go Meeting.  Move to F13Target, will accept into F13 final a well tested fix for this issue considering the potential negative press.

--- Additional comment from updates on 2010-05-12 15:20:53 EDT ---

anaconda-13.42-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/anaconda-13.42-1.fc13
Comment 2 Chris Lumens 2010-05-13 21:36:11 UTC 
*** Bug 592060 has been marked as a duplicate of this bug. ***
Comment 3 RHEL Program Management 2010-05-13 21:40:39 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 4 Ray Strode [halfline] 2010-05-14 02:31:51 UTC 
The default timeout in grub for RHEL was changed to be non-zero regardless of what other OSes are installed some time before the alpha, right?
Comment 5 Hans de Goede 2010-05-17 09:35:40 UTC 
(In reply to comment #4)
> The default timeout in grub for RHEL was changed to be non-zero regardless of
> what other OSes are installed some time before the alpha, right?    

Right.

installclasses/rhel.py:

class InstallClass(BaseInstallClass):

    bootloaderTimeoutDefault = 5

But we have (had ?) some issues with product.img loading causing us to use the Fedora install class for RHEL installs, this is being tracked in another bug.
Note You need to log in before you can comment on or make changes to this bug.