Bug 465816

Summary:	Traceback starting VNC in kickstart install
Product:	[Fedora] Fedora	Reporter:	Orion Poplawski <orion>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	anaconda-maint-list, dcantrell
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-10-06 15:39:19 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:

Description Orion Poplawski 2008-10-06 15:23:17 UTC

Description of problem:

PXE/kickstart install.

After "Starting VNC"

Traceback (most recent call last):
  File "/usr/bin/anaconda", line 850, in <module>
    runVNC()
  File "/usr/bin/anaconda", line 427, in runVNC
    vncS.startServer()
  File "/usr/lib/anaconda/vnc.py", line 221, in startServer
    self.initialize()
  File "/usr/lib/anaconda/vnc.py", line 101, in initialize
    netinfo = network.Network()
  File "/sur/lib/anaconda/network.py", line 301, in __init__
    available_devices = self.available()
  File "/usr/lib/anaconda/network.py", line 359, in available
    elif ksdevice.find(':') != -1:
AttributeError: 'NoneType' object has no attribute 'find'

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

Comment 1 Chris Lumens 2008-10-06 15:39:19 UTC


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