Bug 497390

Summary: autopart puts PReP and '/boot' on different disks
Product: [Fedora] Fedora Reporter: James Laska <jlaska>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: anaconda-maint-list, jturner, pjones, rmaximo, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-05-06 17:24:44 EDT Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 495965    

Description James Laska 2009-04-23 13:06:42 EDT
Description of problem:
On an IBM power5 system, autopart puts the PReP and '/boot' partitions on different disk.  Due to a yaboot limitation (I think), these partitions must exist on the same disk.

Version-Release number of selected component (if applicable):
anaconda-11.5.0.47

How reproducible:
every autopart install

Steps to Reproduce:
https://fedoraproject.org/wiki/QA:Testcase_Anaconda_autopart_install
  
Actual results:
While partitioning will work, yaboot is unable to boot in such a scenario.

Expected results:
In F10 and RHEL5, PReP and '/boot' are always on the same disk (typically sda1 and sda2).

Additional info:
Comment 1 Chris Lumens 2009-05-05 15:30:00 EDT
This should be fixed in the next build of anaconda.  Thanks for the bug report.
Comment 2 Chris Lumens 2009-05-06 17:24:44 EDT
Actually, I tested this on ppc as well, so moving to CLOSED.