Bug 74180 - partition without mountpoint: crash
Summary: partition without mountpoint: crash
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: installer
Version: 7.3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-09-17 14:12 UTC by Jure Pecar
Modified: 2007-04-18 16:46 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 18:49:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Jure Pecar 2002-09-17 14:12:44 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827

Description of problem:
If i create some partitions without mountpoints in disk druid, installer crashes
after formating the filesystems.

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


How reproducible:
Always

Steps to Reproduce:
1.in disk druid, create some partitions.
2.define mountpoints for some, but not all.
3.continue with instalation.

Actual Results:  Installer pops up a python exception after formating
filesystems and before 'setting up rpm transaction'.


Expected Results:  I would like/expect it to make the partitions, but leave them
unmounted. Disk Druid offers this possibility, so either make it work or somehow
force every partition created to have a mount point assigned.

Additional info:

This also happens if i define partitions as 'software raid'. For example, i'd
like to create some raid linear 'arrays', which i cannot do in the installer,
but would like to have the partitions already waiting for me after the
installation.

Comment 1 Jeremy Katz 2002-11-07 00:18:15 UTC
Could you attach the traceback that you get?

Comment 2 Michael Fulbright 2002-12-02 16:10:31 UTC
Closing due to inactivity, please reopen if you have additional information to add.

Comment 3 Red Hat Bugzilla 2006-02-21 18:49:38 UTC
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.