[opensuse-autoinstall] AutoYast SLES9 SP3 problem with hostname via DHCP
Hello,
I am facing a problem that I cannot solve myself and hope for your expert help.
Description:
When installing a machine with SLES9 with AutoYast the via DHCP forwarded hostname is not fully
recognized.
Environment:
1. DHCP-Server under SLES9 SP3
2. DNS via Active Directory under Windows 2003 Server
3. PXE and Installationsserver for Autoyast under SLES9 SP3
4. various Destination Machines
(3. und 4. under VMware ESX 3)
Procedure:
In my environment every Machine is assigned a fixed IP-Adress and the corresponding host name via DHCP
(this is the assignment for the time being and should not be changed). The installation of new Linux
machines via AutoYast works basically fine so far. The installations are triggert with PXE-Boot over the
Network. For the basic installation I have created various XML Files for AutoYast.
eth_default_dhcp.xml:
--------------------------------------------------------------------------------
<?xml version="1.0"?>
<!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd">
<profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns">
<configure>
<networking>
<dns>
On Fri, Jan 11, 2008 at 12:32:10PM +0100, chrroe@uni.de wrote:
The problem is, that in the first part of the AutoYast installation (when the RPMs are installed) the new machine knows its IP adress but not the Computer Name. Only after the reboot when the second part of the installtion starts, the hostname is set correctly.
I have identified 3 RPMs so far which need the hostname in the first part of the installation (aaa_base, postfix and a custom made one).
I don't know if Uwe or someone else might come back with a more elegant solution (or point out why autoyast isn't doing what it should) but I do know you could fix this with a pre script. You could have a pre script see what hostname is associated with the IP it has (assuming your rDNS updates for your dhcp values too) and create a /tmp/profile/modified.xml with a <hostname> line like you mentioned trying in a test. I'm using this profile re-write ability pretty extensively to configure the networking/hostname on the fly myself. I have placeholders in the profile file like: <comment>ADDON_DEFAULTS</comment> <comment>NIS_DEFAULTS</comment> <comment>NTP_DEFAULTS</comment> <comment>ROOTWORD_DEFAULT</comment> <comment>TZ_DEFAULT</comment> Then I have a pre.sh script that walks the file and functions that replace the above with values read in from a config file. This allows me to use the exact same scripts/profiles at each of our offices with each local admin setting the initial values to suit their needs. My entire networking section looks like: <networking> <comment>NET_DEFAULTS</comment> </networking> And the hostname, IP, etc are all put into place and then autoyast reads in the updated file before starting it's processing. Next I'm going to add in the ability to size swap based on the amount of physical ram with a multiple set by admins when they run the script that sets up the files the installer uses. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Drew: "Violence doesn't solve anything? World War I. World War II. Star Wars. every Super Bowl. Who says violence doesn't solve anything?!" ==> Drew Cary Show -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Freitag, 11. Januar 2008, chrroe@uni.de wrote:
1. DHCP-Server under SLES9 SP3 2. DNS via Active Directory under Windows 2003 Server 3. PXE and Installationsserver for Autoyast under SLES9 SP3 4. various Destination Machines (3. und 4. under VMware ESX 3)
The problem is, that in the first part of the AutoYast installation (when the RPMs are installed) the new machine knows its IP adress but not the Computer Name. Only after the reboot when the second part of the installtion starts, the hostname is set correctly.
Steffen, I think this is an issue since ages isn't it?
I have identified 3 RPMs so far which need the hostname in the first part of the installation (aaa_base, postfix and a custom made one).
that can't be true. I do pxe/DHCP installations all the time and aaa_base never had any problems during the installation.
For testing, I addded the hostname to
<hostname>testhost</hostname>
and set
true to false, and then the hostname was "ok" also in the first step of the installation, and all RPMs are installed as expected.
that's hard to believe actually. The <networking> section is not evaluated by autoyast in the first stage. Whatever you do there, it can't have any influence in stage 1. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: Purity by Dismantled -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On Mon, 21 Jan 2008, Uwe Gansert wrote:
On Freitag, 11. Januar 2008, chrroe@uni.de wrote:
1. DHCP-Server under SLES9 SP3 2. DNS via Active Directory under Windows 2003 Server 3. PXE and Installationsserver for Autoyast under SLES9 SP3 4. various Destination Machines (3. und 4. under VMware ESX 3)
The problem is, that in the first part of the AutoYast installation (when the RPMs are installed) the new machine knows its IP adress but not the Computer Name. Only after the reboot when the second part of the installtion starts, the hostname is set correctly.
Steffen, I think this is an issue since ages isn't it?
Well, linuxrc did never set the hostname. So if it is an issue, then it has always been. OTOH it's not a big deal to run 'dhcpcd -H' if that would help you. Steffen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (4)
-
chrroe＠uni.de -
Mike Marion -
Steffen Winterfeldt -
Uwe Gansert