Bug 680364

Summary:	Anaconda should not stop if /boot is on an LV
Product:	Red Hat Enterprise Linux 6	Reporter:	Dannie Obbink <dannieobbink>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED NOTABUG	QA Contact:	Release Test Team <release-test-team>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.1
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-02-25 15:21:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Dannie Obbink 2011-02-25 09:22:57 UTC

When trying to create a partition for /boot on an LV, anaconda tells me "Should be on a bootable partition".

GRUB2 (and possibly others), ARE able to boot from an LV.

Thus, Anaconda should not block /boot to be on a LV, as there's no guarantee that the bootloader used will be the GRUB Legacy, distributed with the installer (e.g. when dual-booting with a different Linux distro).

Anaconda is ofcourse entitled to give a big warning on this, but should not block the install.

On a more personal note:
This is the only thing from keeping me from just PV'ing /dev/sda :)

Comment 2 Chris Lumens 2011-02-25 15:21:12 UTC

grub is the official bootloader for RHEL6, so that's what we have to program for.  We must block because the bootloader we use does not support /boot on LVM (at least not on x86) and we can have no guarantees as to what you may be setting up later.  This situation may be resolved for RHEL7, though.