May 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

sles9-s390 autoyast
by Stefan Leippert 12 May '05

12 May '05

Hello ! I am trying to install SLES-9 s390 with autoyast from our local install server on zSeries. I read the manual and tried to get it work, but maybe there are some basic understanding problems: I have a control file (written in XML, made by yast2 and parsed ok) where all necessary data is stored in (IP-Adresses, DASD-IDs, Partitioning, Package Selection etc.) The control file is on our local FTP-Server. On our installation server there are only ISO-Files of the installation CDs, which are mounted loopback (incl. SP1...). A simple remote installation with ssh with ramdisk, yast etc. works fine. It is not possible to use a CD-ROM or floppy for the control file. But I can make changes to the iso-files. Which file on the ISOs have to be changed to get the system to load my control-file for autoinstallation? Thank you for your help ! Stefan

2 1

Problems finding autoinst.xml on floppy
by Thorbjorn Jemander 11 May '05

11 May '05

Hello, I'm new to suse and yast2/autoyast. I've got suse professional 9.3 and want to install that on a number of machines. I've created an autoinst.xml file (from using "yast2 autoyast") that I've put on a 3.5" floppy (MSDOS formatted). The autoinst.xml file passes xmllint without comments, and it looks OK. The floppy does not contain any info file. The problem: I put in the DVD and the floppy and boot. Apparantly, the autoinst.xml file should be detected automatically and turn the installation into an automated one. However, it does not detect the file (it's spelled correctly, I've checked several times). I can see that the disk drive flashes its LED during the first phase of the installation, so it looks like it's at least trying to read the floppy. It does not find it, or at least thinks that something is wrong with it, since it always proceeds to manual install. If I explicitly specify autoyast=floppy, or autoyast=floppy://autoinst.xml (in the first installation screen) it also tries to read the floppy, but then I end up in the ncurses installer where I get the message "Could not find the SUSE Linux Installation Source, Activating manual setup program". What does that mean? I've tried with two different floppy disks, so that it's not the disk that is broken. The disk drive is working under normal suse (KDE) operation, so it does not seem like that that is broken either. What am I doing wrong? - Is a MSDOS-formatted floppy disk OK? - Is the content of the autoinst.xml file wrong? The XML syntax seems to be fine, but how can I tell whether the installer thinks that the contents makes no sense? How can I verify that the *installer* thinks the autoinst.xml file is OK? - Do I need an info file on the floppy? - Can't I do this floppy autoinstallation with the factory SuSE 9.3 CDs/DVDs? The autoinst.xml file: ----------------------------------8<----------- <?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> <groups config:type="list"> <group> <groupname>video</groupname> <userlist>tsslab</userlist> </group> <group> <groupname>dialout</groupname> <userlist>tsslab</userlist> </group> </groups> <networking> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <dhcp_resolv config:type="boolean">false</dhcp_resolv> </dns> <interfaces config:type="list"> <interface> <bootproto>static</bootproto> <broadcast>192.168.0.255</broadcast> <device>eth0</device> <ipaddr>192.168.0.20</ipaddr> <name>Ethernet Network Card</name> <netmask>255.255.255.0</netmask> <network>192.168.0.0</network> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <modules config:type="list"> <module_entry> <device>static-0</device> <module></module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <runlevel> <default>5</default> <services config:type="list"> <service> <service_name></service_name> </service> </services> </runlevel> <scripts> <post-scripts config:type="list"> <script> <filename>postinstall</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[echo "Postinstallation script is running!"]]></source> </script> </post-scripts> <pre-scripts config:type="list"> <script> <filename>preinstall</filename> <interpreter>shell</interpreter> <location></location> <source><![CDATA[echo "Preinstallation script is running!"]]></source> </script> </pre-scripts> </scripts> <user_defaults> <expire></expire> <group>100</group> <groups>video,dialout</groups> <home>/home</home> <inactive>-1</inactive> <shell>/bin/bash</shell> <skel>/etc/skel</skel> </user_defaults> <users config:type="list"> <user> <encrypted config:type="boolean">true</encrypted> <fullname>tsslab</fullname> <gid>100</gid> <home>/home/tsslab</home> <password_settings> <expire></expire> <flag></flag> <inact>-1</inact> <max>99999</max> <min>0</min> <warn>7</warn> </password_settings> <shell>/bin/bash</shell> <uid>1000</uid> <user_password>$2a$05$CdvjoC.h6A5UWVx1hVXMzu/eI9CdA467wf4YX.LDWaUNuicm Z1Ss2</user_password> <username>tsslab</username> </user> </users> <x11> <color_depth config:type="integer">24</color_depth> <configure_x11 config:type="boolean">true</configure_x11> <display_manager>kdm</display_manager> <enable_3d config:type="boolean">false</enable_3d> <monitor> <display> <max_hsync config:type="integer">82</max_hsync> <max_vsync config:type="integer">75</max_vsync> <min_hsync config:type="integer">31</min_hsync> <min_vsync config:type="integer">58</min_vsync> </display> <monitor_device>1280X1024@75HZ</monitor_device> <monitor_vendor> LCD</monitor_vendor> </monitor> <resolution>1280x1024</resolution> <window_manager>kde</window_manager> </x11> </configure> <install> <general> <clock> <hwclock>localtime</hwclock> <timezone>Europe/Stockholm</timezone> </clock> <keyboard> <keymap>swedish</keymap> </keyboard> <language>en_US</language> <mode> <confirm config:type="boolean">false</confirm> <forceboot config:type="boolean">true</forceboot> </mode> <mouse> <id>00_ps2</id> </mouse> </general> <partitioning config:type="list"> <drive> <device>/dev/hda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <fs_options> <opt_format> <option_blank config:type="boolean">true</option_blank> <option_str>--format</option_str> <option_value>auto</option_value> </opt_format> <opt_hash> <option_blank config:type="boolean">true</option_blank> <option_str>--hash</option_str> <option_value>auto</option_value> </opt_hash> </fs_options> <loop_fs config:type="boolean">false</loop_fs> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <size>30000</size> </partition> <partition> <crypt>twofish256</crypt> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <size>500</size> </partition> <partition> <crypt>twofish256</crypt> <format config:type="boolean">false</format> <loop_fs config:type="boolean">false</loop_fs> <mount></mount> <partition_id config:type="integer">130</partition_id> <size>auto</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <software> <addons config:type="list"> <addon>Basis-Sound</addon> <addon>Kde-Desktop</addon> <addon>Min</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>default</base> <packages config:type="list"> <package>ddd</package> <package>ethereal</package> <package>ethtool</package> <package>ipgrab</package> <package>iptraf</package> <package>netboot</package> <package>nttcp</package> <package>perl-Net-Telnet</package> <package>rinetd</package> <package>tcpd-devel</package> <package>trafmon</package> </packages> </software> </install> </profile> --------------->8-------------------------------- ________________________________________________ Dr. Thorbjörn Jemander, Senior/RT Systems Expert Enea Epact AB, Teknikringen 8, Linköping, Sweden thje(a)epact.se, +46 13 465 58 67, www.epact.com

4 6

Wrong URL for CD2 with installations over nfs
by mayrs＠RZ.FH-Augsburg.DE 11 May '05

11 May '05

Hi I tried to use autoyast for SLES9 over nfs. After I pass SLES CD1, CORE CD1 and reach CORE CD2 I get an error "Insert Media SUSE CORE Version 9 CD 2 ERROR(Media: not attached)". The given URL for the media is nfs://10.128.1.20/local/software/suse/SLES9//core-i386/CD2 The same error for cd 3,4,5 Where does this double-slash between SLES9 and core-i386 come from? Thanks, Stefan Mayr

1 0

SuSE 9.3 install with updates
by Volkmar Glauche 10 May '05

10 May '05

Hi all, I am trying to set up a NFS repository for autoinstall of SuSE Professional 9.3. Problems arise when I try to integrate the latest updates using the scripts create_update_source.sh and create_package_descr (Anas: create_update_source.sh as published on the web does only work correctly when started in the root directory of the installation source, otherwise it doesn't find the original EXTRA_PROV file). But this is not the main problem: after including the updates as described and running create_package_descr, some packages fail to install with md5 checksum and other errors (both updated and original packages). However, this does not seem to be reproducible: I installed an AMD64/64bit which failed first on glibc from the original sources. Then I installed a XEON/32bit, again failure on the glibc. However, the same XEON, installing 64bit now, did not fail at glibc, but at some later point. Both the original source and the updates seem to be ok themselves. NFS installation from the vanilla sources and updating from the updated rpms works. Has anyone seen something similar? Might this be an NFS related issue (no relevant error logs on the NFS server side, though)? I can provide y2logs from the last install in case they would help debugging. -- Volkmar Glauche - Department of Neurology volkmar.glauche(a)uniklinik-freiburg.de Universitaetsklinikum Freiburg Phone 49(0)761-270-5331 Breisacher Str. 64 Fax 49(0)761-270-5310 79106 Freiburg

1 0

RE: [suse-autoinstall] Network Installation Problems
by Paul Anthony Rae (QC/EMC) 10 May '05

10 May '05

Quite sure. The distro I have is 9.0 enterprise, I have checked and double checked. Also I was able to complete an interactive network installation just fine so I haven't the foggiest what is going wrong when I try to get it to auto-install. Is the request for driverupdate triggered by the control file? Is it possible somehow the control file I have generated is asking for it, or needs to be set to ignore it or somesuch? It's the only thing I can think of, but I can't see anything in the control file that clues me in to what is happening. Paul -----Original Message----- From: Michael Marion [mailto:mmarion@qualcomm.com] Sent: May 9, 2005 6:20 PM To: Paul Anthony Rae (QC/EMC) Cc: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] Network Installation Problems On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

Re: [suse-autoinstall] Network Installation Problems
by Michael Marion 09 May '05

09 May '05

On 9 May, Paul Anthony Rae (QC/EMC) wrote: > The problem seems to be that it's trying to download "driverupdate" from the > source directory, but no such file exists. After it can't find that file > the Installation stops with "Error in Installation". Are you sure you're not booting from the sp1 cd's linux kernel and initrd files? I don't think I've ever seen a non-sp installer look for the driverupdate file. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

Re: [suse-autoinstall] Customizing Package Selection and Network Setting
by Michael Marion 09 May '05

09 May '05

On 9 May, Akira Ijuin wrote: > For example, yast/autoyast will automatically install a predefined > set of RPMs when Print Server support is selected. How does one go > about modifying this predefined set? I _think_ that you can edit the .sel files under the SLES (the SLES disk, not UL) directory, under suse/setup/descr then rerun the create_package_descr program to rebuild the descr files. -- Mike Marion-Unix SysAdmin/Staff Engineer-http://www.qualcomm.com Homer: "I'm not normally a religious man, but if you're up there, save me, Superman!" -- Simpsons

1 0

Customizing Package Selection and Network Setting
by Akira Ijuin 09 May '05

09 May '05

Hi, Does anybody have information on doing the following things on autoyast? This is on SLES9 for x86_64. 1. Change the RPM packages that are installed when installing any given installation packages defined by yast/autoyast? For example, yast/autoyast will automatically install a predefined set of RPMs when Print Server support is selected. How does one go about modifying this predefined set? Similarly, a minimal install is done when no extra install packages are selected. How does one go about defining what gets installed during minimal install? 2. Force a network interface to full duplex during installation with autoyast? Also, how is this done during regular bootup from disk? During server startup the interface gets set to half duplex. How does one force it to be full duplex both from autoyast startup and regular machine bootup? I would appreciate any help on this. Please let me know if anything I've said is unclear. Regards, Akira

1 0

Network Installation Problems
by Paul Anthony Rae (QC/EMC) 09 May '05

09 May '05

Hi all, I am encountering a serious difficulty installing an HP DL-385 ProLiant using PXE boot and NFS source. I am trying to do an automatic, hands off installation of SuSE 9.0 Enterprise Server, but the installation fails everytime just after the server recovers the control.xml file from the boot server. The problem seems to be that it's trying to download "driverupdate" from the source directory, but no such file exists. After it can't find that file the Installation stops with "Error in Installation". >From what I have gleaned, "driverupdate" is included in Service Packs. However I am simply trying to install 9.0 with no service packs so how do I get past this difficulty? Any help appreciated, Paul Rae System Inegrator, MMS Ericsson Canada

1 0

Fwd: [suse-autoinstall] auto updating install tree
by Ashe Canvar 06 May '05

06 May '05

I am still not clear about the process of getting the updates from SuSe. 1. The command line (online_update) does not have any parameters for passing my portal username and password. 2. I don't want to use the GUI because I want to script this. 3. man online_update does not exist. -h is very little help either. 4. If I use the gui via YaST2 then the patches get downloaded in /var/lib/Yast2/you/blah.. This happens for the i386 architecture by default. How do I also do this for the x86_64 architecture ? (SLES9). 5. There do not seem to be too many rpms doenloaded after step 4. But a lot of patch-xxx files. What do I do with these ? 6. What do I do with .patch.rpm packages ? I am so confused that I would rather go back to freebsd and its awesome cvsup system. Any help would be appreciated esp with the command lines to get the updates and info on what parts of the downloaded tree to move into the updates folder created by Anas's script. Thanks! On 4/27/05, Ashe Canvar <acanvar(a)gmail.com> wrote: > Perfect. I got the script after some digging. Will let you know if this works. > > http://www.suse.de/~nashif/autoyast2/scripts/create_update_source.sh > > On 4/24/05, Anas Nashif <nashif(a)suse.de> wrote: > > Hi, > > > > If you dont know it by now, there is a command line utility for YOU > > > > /usr/bin/online_update > > > > What you can do is download all updates (download only) to the server, > > create an update source with the script I have posted some weeks ago and > > copy the rpms to this new source and recreate the package database > > everytime something changes. All those steps can be automated using a > > smart script run by cron. > > > > Then you can install new machines with the new packages and without the > > need to run YOU afterwards... > > > > > > Anas > > > > Ashe Canvar wrote: > > > Hi all, > > > > > > I am tryng to make a fully automated installation system for SLES9 for > > > x86_64 and i386. First of all I must congratulate Suse for such an > > > excellent, well thought out installation automation system. Yast does > > > have its issues, but once I learnt the ropes it has made me pretty > > > productive. > > > > > > The issue I am not clear about is as follows: > > > > > > - I created my base install image following the docs in > > > http://www.suse.de/~nashif/autoinstall/9.1/html/ch05s02.html#id2523126 > > > > > > - if I install 20 machines and then YOU them then it takes a long > > > time, even if I run a local YOU server. > > > > > > - What I ideally want is to update the installation tree I have > > > created above such that doing a YOU update post-install is not even > > > required. > > > > > > Is there any way to accomplish this ? > > > > > > How do I download the rpm's that have been released as updates to the > > > base SLES9 release ? Doing that through the portal site is pretty > > > painful/manual. > > > > > > I would ideally like to automate this if possible as a weekl > > > build/test/publish cycle for my organization. > > > > > > Thanks! > > > > > >

2 2