Red Hat Bugzilla – Bug 100418
VNC based install doesn't setup networking for CD based install
Last modified: 2007-04-18 12:55:57 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Description of problem:
Just tried the new VNC based install feature which is really cool, but
anaconda neither asks for an IP address nor uses DHCP to get an IP address.
It's really hard to connect to a VNC server without any IP address assigned.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try a VNC based install
2. no IP address is assigned
What were you installing from?
BTW: The install went fine after I manually setting the IP address using
ifconfig on console #2.
*** Bug 100990 has been marked as a duplicate of this bug. ***
Fixed in development branch.
does the fix in the devel branch implement the networking setup
specified in the kickstart file or an another intermediate setting?
I'm doing a HD only install on a headless machine that requires
moving the HD back and forth between hardware. When connected to a
machine with a monitor it gets to the phase of initiating the vnc
connection based on the vnc --conect directive in the kickstart file.
The static IP info in the kickstart file doesn't seem to be applied.
The destination machine doesn't see any connects or arping for the
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be
fixed). If any of these are still a problem, please reopen or file a new bug
against the release which they're occurring in so they can be properly tracked.