Red Hat Bugzilla – Full Text Bug Listing
|Summary:||lets you add LVM component partitions to the grub boot menu|
|Product:||[Fedora] Fedora||Reporter:||Bill Nottingham <notting>|
|Component:||anaconda||Assignee:||Anaconda Maintenance Team <anaconda-maint-list>|
|Status:||CLOSED RAWHIDE||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-04-14 12:26:28 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:|
Description Bill Nottingham 2008-03-14 12:26:32 EDT
Description of problem: Seems fishy. Although starting to filter the display there could get you into more trouble. Version-Release number of selected component (if applicable): rawhide-20080314
Comment 1 Jeremy Katz 2008-03-14 18:17:12 EDT
On which screen? We're just going off of disks as far as I can tell from looking at the code
Comment 2 Bill Nottingham 2008-03-17 11:29:45 EDT
The 'choose other partitions to boot' widget.
Comment 3 Jeremy Katz 2008-03-17 15:46:44 EDT
Oh, you mean the partitions which are _part_ of a volume, not the volumes themselves. We've actually allowed this forever. But easy enough to filter out LVM (and RAID) components
Comment 4 Jesse Keating 2008-04-03 15:28:33 EDT
Think this could be done for F9, or should we punt for F10? Since this has been allowed before, I don't see it as being an F9 blocker. The bug is in Modified state, so maybe the fix is already done and we just need a retest?
Comment 5 Jeremy Katz 2008-04-03 15:37:37 EDT
The definition of the MODIFIED state is "a fix has been committed"
Comment 6 Jon Stanley 2008-04-14 12:26:28 EDT
Tested: Installing onto single disk. Several other disks (not used in install) were previously part of a raidset. Attempted to add at 'boot loader operating system list' screen, and the only device presented was /dev/sda1 (as would be expected - /dev/sda2 is an LVM partition, and the remaining disks are RAID). Closing