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.
Bug 573223 - Anaconda custom layout does not detect existing LVM volumes
Summary: Anaconda custom layout does not detect existing LVM volumes
Keywords:
Status: CLOSED DUPLICATE of bug 568460
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-13 14:38 UTC by Mohd Izhar Firdaus Ismail
Modified: 2010-03-15 14:55 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-15 14:55:34 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Mohd Izhar Firdaus Ismail 2010-03-13 14:38:25 UTC 
Description of problem:
existing LVM volumes on harddisk were not detected in the custom layout partitioning option

Version-Release number of selected component (if applicable):
anaconda-13.32-1.fc13.i686

How reproducible:
Everytime

Steps to Reproduce:
1. Boot F13 alpha on a machine with existing LVM volumes
2. start install-to-harddisk
3. follow through the wizard until the point where it asked for partitioning options. 
4. select custom

  
Actual results:
Only a list of physical volumes

Expected results:
list of both physical and lvm volumes

Additional info:
Comment 1 Hans de Goede 2010-03-15 11:57:06 UTC 
Please try installing to hard disk again, and when you've arrived at the point where the problem is collect the various anaconda log files you can find under /tmp/*.log and attach them here.
Comment 2 Chris Lumens 2010-03-15 14:55:34 UTC 

*** This bug has been marked as a duplicate of bug 568460 ***
Note You need to log in before you can comment on or make changes to this bug.