Bug 463712
Summary: | [LTC 6.0 FEAT] 200829:UEFI support - grub | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | IBM Bug Proxy <bugproxy> |
Component: | grub | Assignee: | Peter Jones <pjones> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.0 | CC: | atodorov, ejratl, notting, snagar |
Target Milestone: | alpha | Keywords: | FutureFeature |
Target Release: | 6.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Fixed In Version: | grub-0.97-60 | Doc Type: | Enhancement |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-11-10 20:35:35 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: | 598572 | ||
Bug Blocks: | 356741, 464553, 495116, 495132, 511114, 511881, 511889, 511890, 511891, 511948, 512362, 512364, 515064, 519844, 554552, 554559, 555224, 555228 |
Description
IBM Bug Proxy
2008-09-24 07:51:14 UTC
This feature exists in the current Fedora beta release. The feature requested has already been accepted into the upstream code base planned for the next major release of Red Hat Enterprise Linux. When the next milestone release of Red Hat Enterprise Linux 6 is available, please verify that the feature requested is present and functioning as desired. in Red Hat CVS Tree Marking as Accepted Switching Severity from Urgent to High. Urgent should be reserved for problems that need to be fixed asynch. ------- Comment From garyhade.com 2010-06-04 13:54 EDT------- Verification completion depends on resolution of the following issue. LTC bug 64356 - RIT961823- first boot failure on system with internal USB drive https://bugzilla.linux.ibm.com/show_bug.cgi?id=64356 Red Hat bug 598572 - first boot failure on system with internal USB drive https://bugzilla.redhat.com/show_bug.cgi?id=598572 ------- Comment From garyhade.com 2010-07-06 18:12 EDT------- Verification is still awaiting resolution of the issue mentioned in the previous comment. We are waiting to hear the results of the Red Hat engineering review. IBM, can you perform the UEFI install/boot test on a system that doesn't have USB disks connected to work around bug #598572 ? ------- Comment From garyhade.com 2010-07-13 13:00 EDT------- (In reply to comment #10) > IBM, > can you perform the UEFI install/boot test on a system that doesn't have USB > disks connected to work around bug #598572 ? Yes, if no internally or externally connected USB drives are present during the install we do not see the first boot failure. HOWEVER, as indicated in the bug, if any USB drives are added following installation (e.g. by someone inserting USB key or introducing a media tray containing a USB drive) a boot or reboot will fail. The workaround you are suggesting would not be reasonable for systems with internal USB drives because the system would have to be opened up to remove the USB key prior to installation and the subsequent replacement of the key following installation would cause boot/reboot to fail in the same way it would if an externally connected USB drive was connected after the install. IBM, thanks for the update. As per comment #9 I'm moving this bug to VERIFIED. The remaining issues with internal/external USB drives is in bug #598572. Post all you additional comments there. ------- Comment From garyhade.com 2010-07-14 15:52 EDT------- I have been working under the misunderstanding that all bugs reported against a feature needed to be resolved before the Distro State can be moved to VERIFIED. I just found out that a feature can be marked as VERIFIED before all the open issues reported with respect to it have been resolved. So, I am moving this one to VERIFIED before the open issue I mentioned above is closed. Red Hat Enterprise Linux 6.0 is now available and should resolve the problem described in this bug report. This report is therefore being closed with a resolution of CURRENTRELEASE. You may reopen this bug report if the solution does not work for you. |