Bug 69169 - traceback when trying to add a partition on a specific disk to fill disk
Summary: traceback when trying to add a partition on a specific disk to fill disk
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: redhat-config-kickstart
Version: limbo
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Tammy Fox
QA Contact:
URL:
Whiteboard:
: 68148 (view as bug list)
Depends On:
Blocks: 67217
TreeView+ depends on / blocked
 
Reported: 2002-07-18 16:50 UTC by Tammy Fox
Modified: 2008-05-01 15:38 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-07-21 03:28:16 UTC
Embargoed:

Attachments (Terms of Use)

Description Tammy Fox 2002-07-18 16:50:18 UTC 
Traceback (most recent call last):
  File "/usr/share/redhat-config-kickstart/partWindow.py", line 187, in
on_ok_button_clicked
    rowData = self.getData()
  File "/usr/share/redhat-config-kickstart/partWindow.py", line 253, in getData
    selectDialog.hide()
NameError: global name 'selectDialog' is not defined

I selected /home, ext3, fill, ondisk hdb, and format. When I clicked OK, 
I get the above traceback, and a dialog pops up that says I must specify
a size for the partition.

It successfully let me create 2 partitions on hda (the / to fill the drive and
/boot set to 75MB) before giving me this.
Comment 1 Tammy Fox 2002-07-18 16:58:26 UTC 
I fixed the traceback in CVS, but it still tells me to specify a size
even if I select fill -- the size pulldown menu is blank (even though
it is grayed out). If it is grayed out with a value, it doesn't tell me
this. Should be easy to fix.
Comment 2 Tammy Fox 2002-07-18 17:14:29 UTC 
I fixed my own bug. If fill is selected, it doesn't display the dialog about
having to specify a size. Please verify in 2.3.1-1.
Comment 3 Tammy Fox 2002-07-19 02:12:45 UTC 
*** Bug 68148 has been marked as a duplicate of this bug. ***
Comment 4 Jay Turner 2002-07-29 16:52:50 UTC 
Fix confirmed with redhat-config-kickstart-2.3.2-3.
Note You need to log in before you can comment on or make changes to this bug.