Red Hat Bugzilla – Bug 470559
F10 anaconda failed to start vnc server
Last modified: 2009-02-16 15:32:43 EST
I tried installing a KVM guest by passing "vnc" on the anaconda command line and when it tried to start the vnc server I got a traceback:
Running anaconda 18.104.22.168, the Fedora system installer - please wait...
18:26:05 Starting VNC...
Traceback (most recent call last):
File "/usr/bin/anaconda", line 859, in <module>
File "/usr/bin/anaconda", line 432, in runVNC
File "/usr/lib/anaconda/vnc.py", line 206, in startServer
File "/usr/lib/anaconda/vnc.py", line 122, in initialize
self.name = network.getDefaultHostname(self.anaconda)
File "/usr/lib/anaconda/network.py", line 115, in getDefaultHostname
hn = anaconda.id.network.hostname
AttributeError: 'NoneType' object has no attribute 'network'
Interesting problem. Can't reproduce it on anything but a kvm guest. Installing on one of my test boxes here, it works fine. Here's the patch:
diff --git a/network.py b/network.py
index c986cda..45dc408 100644
@@ -112,7 +112,10 @@ def getDefaultHostname(anaconda):
if hn and hn != 'localhost' and hn != 'localhost.localdomain':
- hn = anaconda.id.network.hostname
+ hn = anaconda.id.network.hostname
+ hn = None
if not hn or hn == '(none)' or hn == 'localhost' or hn == 'localhost.localdomain':
hn = socket.gethostname()
BTW, 'patch-review' in the devel whiteboard is for my own purposes. I've submitted the patch to the rest of the anaconda team for review. If I can merge it in to repository, I'll move the bug to MODIFIED.
Fix will be in anaconda-22.214.171.124-1.
*** Bug 470877 has been marked as a duplicate of this bug. ***
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here: