Bug 697886

Summary: TypeError: 'NoneType' object is not subscriptable
Product: [Fedora] Fedora EPEL Reporter: Jeffrey C. Ollie <jeff>
Component: cobblerAssignee: James C. <jimi>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: el5CC: awood, dgoodwin, jimi, jonathan, shenson, vanmeeuwen+fedora
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: anaconda_trace_hash:4394abaaf121d3fc275dbfb785ceab3d807c9fcec9e3f43e942efb11fcf3343e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-17 01:53:08 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Attached traceback automatically from anaconda.
none
Attached traceback automatically from anaconda. none

Description Jeffrey C. Ollie 2011-04-19 14:55:24 UTC
The following was filed automatically by anaconda:
anaconda 15.27 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 395, in update
    bootif_mac = flags.cmdline.get("BOOTIF")[3:].replace("-", ":").upper()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 352, in __init__
    self.update()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/__init__.py", line 154, in network
    self._network = network.Network()
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 589, in execute
    devices = self.anaconda.network.netdevices
  File "/usr/lib64/python2.7/site-packages/pyanaconda/kickstart.py", line 1212, in execute
    obj.execute()
  File "/usr/sbin/anaconda", line 920, in <module>
    anaconda.ksdata.execute()
TypeError: 'NoneType' object is not subscriptable

Comment 1 Jeffrey C. Ollie 2011-04-19 14:55:27 UTC
Created attachment 493212 [details]
Attached traceback automatically from anaconda.

Comment 2 Jeffrey C. Ollie 2011-04-19 14:57:13 UTC
Was tying to do an install using Cobbler onto a VMWare guest.

Comment 3 Chris Lumens 2011-04-19 15:05:57 UTC
If you use "ksdevice=bootif", we look for the BOOTIF= kernel command line parameter which should be automatically added by whatever boots the system - so, pxeboot or the like.  It looks like VMWare's not adding that parameter.  The real fix would be for them to correct that.  In the meantime, you may want to consider using ksdevice=eth0.  That looks to be your only network device.

Comment 4 Jeffrey C. Ollie 2011-04-19 15:19:58 UTC
Hmm... Well, would this be more of a Cobbler issue then?  As I believe it's Cobbler adding the ksdevice=bootif option...

Comment 5 Jeffrey C. Ollie 2011-04-19 17:01:19 UTC
Reassigning to cobbler... I'm using Cobbler 2.0.9 on CentOS 5...

Comment 6 Robert Lightfoot 2011-06-14 23:38:21 UTC
Created attachment 504782 [details]
Attached traceback automatically from anaconda.

Comment 7 Robert Lightfoot 2011-06-14 23:52:34 UTC
I was installing F15-i386 to a qemu-kvm guest running on an F14-x86_64 host using cobbler running on Centos 5.6.  This same kickstart works for installing F14-i386 to a qemu-kvm guest on the same F14-x86_64 host without bug.  Looks like an F15 issue to me.

Comment 8 Robert Lightfoot 2011-06-15 00:32:23 UTC
Tried the suggestion of Chris Lumens in Comment 3 and went to the Cobbler-Web GUI and under the System Page for this System added the Kernel Option ksdevice=eth0 which made it work without issue.

Comment 9 James C. 2012-04-17 01:53:08 UTC
Closing as not a bug, if you continue to have issues with this please open an issue at the new github issue tracker for cobbler: https://github.com/cobbler/cobbler/issues