Red Hat Bugzilla – Bug 461493
'ksdevice=link' causes traceback
Last modified: 2008-10-03 14:37:01 EDT
Booting anaconda-220.127.116.11 with 'ksdevice=link' on the commandline causes anaconda to traceback just after starting X. The installer exits, so I can't get the anacdump.txt file, but here's the traceback:
Traceback (most recent call last):
File "/usr/bin/anaconda", line 913, in <module>
anaconda.id = instClass.installDataClass(anaconda, extraModules, opts.display_mode, anaconda.backend)
File "/usr/lib/anaconda/instdata.py", line 291, in __init__
File "/usr/lib/anaconda/instdata.py", line 64, in reset
self.network = network.Network()
File "/usr/lib/anaconda/network.py", line 342, in __init__
I assume this means that self.firstnetdevice is set to 'link'. I'm not sure how it passed this check in Network.available():
if ksdevice and self.netdevices.get(ksdevice) != '':
self.firstnetdevice = ksdevice
but I guess 'link' will have to be handled as a special case there.
Just booted with ksdevice=link and it doesn't traceback, it just doesn't do anything with that boot argument right now. I need to modify the ksdevice=link handling to work with NM now.
But, it doesn't traceback at least.
Got it to traceback using anaconda-18.104.22.168-1.i386 when booting from a boot.iso and providing the cmdline args:
repo=hd:sdc1:/dvd ksdevice=link ip=dhcp noipv6
This seems to work fine now. Jim?
Indeed ... additional test results located at https://fedoraproject.org/wiki/QA/Test_Days/2008-10-02#How_to_test.3F