[rhelv6-beta-list] rhel6 remote installs not working

[Kyle O'Donnell]

I've had problems in the past where sometime after initial boot it renames
interfaces somehow... 

I've since started using:

ksdevice=00:11:22:33:44:55 (MAC address instead of interface name)

--kyleo

On Thu, 5 Aug 2010 16:40:17 -0500, gregwm
<rhelv6-beta-list at greatlakedata.com> wrote:
> i'm trying to do remote installs onto 2 sun x2100 m2's and a sun x2100
> in a
>  datacenter.  both m2's get stuck "Waiting for NetworkManager to
> configure
>  eth0"(or eth1)..."There was an error configuring your network
> interface."
>   the x2100 does not get caught there, it asks for the nfs server
>  information, but it can't seem to find the server nfs directory.  when
>  retrying, it seems images/install.img always gets appended to the
> directory
>  name, but adding those names at the nfs server doesn't help (lacking a
> LOM
>  the x2100 is thus stuck until human hands are available).  here's what
> i
>  give via either grub or pxe:
> 
>     - r6.vmlinuz  initrd=r6.initrd.img lang=en_US keymap=us
> ksdevice=eth1
>     netmask=255.255.255.240 gateway=192.168.0.245 dns=192.168.0.244
>     ip=192.168.0.246 hostname=bleep quiet panic=30 vnc vncpassword=foo
> askmethod
> 
>  Hi Greg,
> 
>  Looking at the command line arguments you're giving, it seems like
> you're doing a kickstart install but not giving a location of a
kickstart
> configuration file?  ie.  adding another argument like:
> 
>   ks=http://10.11.12.13/kickstart/rhel6network.kickstart [1]
> 
>  For me, this approach works.  It tells the RHEL 6 installer where to
> get the more complete details for the installation (ie NFS server
> location and path, list of packages to install, etc).
> 
> 
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Installation_Guide/s1-kickstart2-options.html
> [2]
> 
>  With the x2100, it sounds like this may work if you have access to a
> HTTP server.  The description you gave of the x2100's behaviour sounds
> like the network is configuring ok, but the next bits are getting
> confused when it goes looking for things.
> 
> i do interactive remote installs.  at your prompting i tried
> 
>    ks=nfs:192.168.3.4:/kickstart/pecan.ks
> 
> however i suspect my lack of luck with that on the m2 is for the same
> reason that the rhel6 anaconda fails to configure eth0 as in my post
> above.  i'm less eager to fuss further with the x2100 as i have to get
> help to reboot it when it fails.
> 
> the obvious place to put the ks file is on the local disk, but that
> doesn't work either.  and i found user mention of that working in f10
> but no longer in f11.  sad.
> 
> 
> Links:
> ------
> [1] http://10.11.12.13/kickstart/rhel6network.kickstart
> [2]
>
http://www.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Installation_Guide/s1-kickstart2-options.html