Bug 67034 - mis-leading error if size is too big but "force primary" enabled
mis-leading error if size is too big but "force primary" enabled
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2002-06-19 12:31 EDT by James Manning
Modified: 2007-04-18 12:43 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-04 22:39:51 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description James Manning 2002-06-19 12:31:39 EDT
similar to bug #67031

If attempting to allocate a partition of greater size than available space, if
the "Force to be a primary partition" option is checked, then instead of the
pop-up error dialog saying anything about space (see 67031), the error is "Could
not allocate partitions as primary partitions" which is misleading since the
partitions could not be allocated at all, primary or not.  Simply unchecking the
force and the error goes back to "Could not allocate partitions", as in 67031,
still nothing about size issues
Comment 1 Jeremy Katz 2004-10-04 22:39:51 EDT
Similarly, not going to do this at the moment.

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