Bug 60573 – Anaconda primary partioning

Bug 60573 - Anaconda primary partioning

Summary:	Anaconda primary partioning

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	anaconda (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	i586 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Jeremy Katz
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-03-01 14:00 EST by Need Real Name
Modified:	2007-04-18 12:40 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:48:32 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Need Real Name 2002-03-01 14:00:13 EST

Description of Problem:Installing RH7.2. Windows XP, Celeron processor.  
Automatic Partitioning crashes (keep all partitions, use exiting free space, 
no review).  Error message: "Partitioning failed, Could not allocate 
partitions as primary partitions, Unhandled exception, a bug, Report against 
anaconda."

I copied the detailed error log onto a floppy, but I don't know how to send it 
to you.


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


How Reproducible: Failed in same way 3 times.


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Michael Fulbright 2002-03-05 12:32:21 EST

If you look on this form there is a 'Attachments:' label, and beside it is a
'Create a new attachment' option. Please use that to attach the crash file.

Comment 2 Michael Fulbright 2002-04-10 14:23:28 EDT

Closing due to inactivity, please reopen if you contine to have problems.

Comment 3 Red Hat Bugzilla 2006-02-21 13:48:32 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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