Bug 210260

Summary: install fails immediately at start of package installation
Product: [Fedora] Fedora Reporter: David Miller <davem>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhide   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-10-11 14:36:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 150224    
Attachments:
Description Flags
failure debugging log from installer none

Description David Miller 2006-10-11 02:08:36 UTC 
Description of problem:

Install fails at the installation of the first package.

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


How reproducible:

Every time.

Steps to Reproduce:
1.download boot.iso from devel, boot
2.select packages, customize by adding "software development", "chinese",
"japanese", and "korean" to installation set
3.begin installation
  
Actual results:

Install fails at first package install.

Expected results:

Install succeeds.

Additional info:

Will attach debugging log provided by the installer.
Comment 1 David Miller 2006-10-11 02:08:37 UTC 
Created attachment 138211 [details]
failure debugging log from installer
Comment 2 David Miller 2006-10-11 03:49:51 UTC 
test4 i386 DVD fails in a similar fashion, I double checked that the
DVD image was burned correctly:

1) boot into graphical installer
2) select "software development" package group, this issues a prompt indicating
that a network interface is necessary for that selection, say "OK"
3) it tries to bring the network interface up
4) anaconda error triggers

I had to write the following debug backtrace by hand since the installer
didn't give me an option of "scp'ing" the debug log as the boot.iso
case did, but here goes:

Traceback (most recent call first):
 File "/usr/lib/anaconda/iw/netconfig_dialog.py", line 212, in _ok
   if self.rc != gtk.RESPONSE_OK:
AttributeError: 'module' object has no attribute 'RESPONSE_OK'

Local variables in innermost frame:
val: eth0
f: <closed file '/etc/resolv.conf', mode 'w' at 0xa2ffd10>
netdev: DEVICE=eth0
BOOTPROTO=static
HWADDR=00:11:25:D2:42:89
ONBOOT=no

self: <network_dialog.NetworkConfigurator instance at 0xb7b668cc>
args: (<gtk.Button object (GtkButton) at 0xa2e86e4>,)
w: <gui.WaitWIndow instance at 0xa3faeac>
combo: <gtk.ComboBox object (GtkComboBox) at 0xa2e870c>
active: <GtkTreeIter at 0x9f86da0>
ns: 64.81.79.2
Comment 3 David Miller 2006-10-11 03:53:33 UTC 
Backtrace from Pdb of the test4 DVD failure case:

(Pdb) bt
  /usr/bin/anaconda(954)?()
-> anaconda.intf.run(anaconda)
  /usr/lib/anaconda/gui.py(876)run()
-> self.icw.run (self.runres)
  /usr/lib/anaconda/gui.py(1112)run()
-> gtk.main()
  /usr/lib/anaconda/iw/task_gui.py(169)_toggled()
-> ret = net.run()
  /usr/lib/anaconda/iw/netconfig_dialog.py(128)run()
-> gtk.main()
> /usr/lib/anaconda/iw/netconfig_dialog.py(212)_ok()
-> if self.rc != gtk.RESPONSE_OK:
(Pdb)
Comment 4 Jeremy Katz 2006-10-11 14:36:38 UTC 
For the second, please read the announcement for Fc6Pre which had the link to an
updates.img with the fix as well as how to use it.  The first is also a dupe 

*** This bug has been marked as a duplicate of 209462 ***