Bug 164633 - autopartition failure "Unsatisfied partition request"
Summary: autopartition failure "Unsatisfied partition request"
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-07-29 15:06 UTC by Matthew Miller
Modified: 2008-08-02 23:40 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-08-24 21:02:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthew Miller 2005-07-29 15:06:13 UTC
Description of problem:

During the install on some new IBM xSeries 345 rackmount systems, if
autopartition is selected (or if kickstart is used), we get this error:


  Error Partitioning

  Could not allocate requested partitions:

  Unsatisfied partition request
  New Part Request - mountpoint: None uniqueID: 23
   type: physical volume (LVM) format: 1 badblocks: None
   device: None drive: ['sda'] primary: None
   size: 0 grow: 1 maxsize: None
   start: None end: None migrate: None origfstype: None.


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

Happens with various versions of anaconda -- confirmed with 10.1.0.2-1,
10.1.1.13-1 (rebuilt from RHEL) and 10.1.1.19-2 (rebuilt from CentOS/RHEL).


How reproducible:

Always.

Steps to Reproduce:
1. pick autopartitioning or use kickstart
2. boom.
  
Actual results:

Error message as above

Expected results:

It works. :)

Additional info:

Appears fixed in FC4, but Paul Nasrat asked me to file a bug. So here it is.

Probably a dupe of bug #129528 or of super-top-secret bug #131325.

There's been quite a few changes in autopart.py from FC3->FC4, and if you know
what the specific problem is here, that'd be handy, 'cause then I could make the
minimal change locally. Thank you very much!

Comment 1 Matthew Miller 2006-07-10 23:42:59 UTC
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!


Comment 2 Red Hat Bugzilla 2007-06-12 02:53:21 UTC
requested by Jams Antill


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