Bug 689996 - /boot on LVM with EFI system results in traceback
Summary: /boot on LVM with EFI system results in traceback
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-22 23:13 UTC by Brian Lane
Modified: 2011-12-06 10:31 UTC (History)
2 users (show)

Fixed In Version: anaconda-13.21.123-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:31:00 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1565 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-12-06 00:39:12 UTC

Description Brian Lane 2011-03-22 23:13:40 UTC
On EFI the partition editor doesn't throw an error if there is no separate /boot partition setup.

1. Create a default partition layout and edit the settings.
2. Delete the /boot partition
3. Proceed with install.

Traceback in booty/x86.py writeGrubConf because bootDev is a LVM device and you cannot put /boot on an LVM. SanityCheck in storage catches this on non-EFI with the platform.checkBootRequest() but on EFI it sets the boot path to /boot/efi which passes the checks.

Comment 2 RHEL Program Management 2011-06-13 19:51:06 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 4 Pavel Holica 2011-10-26 15:01:16 UTC
Verified fix on RHEL6.2-20111019.2 x86_64 UEFI Server with anaconda-13.21.146-1.el6.

Comment 5 errata-xmlrpc 2011-12-06 10:31:00 UTC
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-2011-1565.html


Note You need to log in before you can comment on or make changes to this bug.