September 2005 - openSUSE Autoinstall - openSUSE Mailing Lists

Autoyast network configuration: "ifcfg-eth--" invalid configuration file.
by Frederico Muñoz 17 Sep '05

17 Sep '05

Hello, I've set up a SuSE install server to automatically install around 15 servers.Everything is working except one crucial thing, the network configuration. I've been struggling with this for hours, and already did so many installs in a test machine that I am close to just giving up on it and just do the network configuration manually on every server. The error is always the same: everything works great (congrats to SuSE and autoyast developers in particular) until it tries to bring up the network that was configured: it becomes obvious from the messages that eth0 and eth1 aren't configured and that instead a single "eth--" interface was created. It stays some seconds "Waiting for mandatory interface: eth--". Upon reboot and a closer inspection a "/etc/sysconfig/network/ifcfg-eth--" exists with the network details of the first interface configured in the autoyast profile. No other interface configuration file is present. I'm still not entirely proficient on the way network configurations are done in SuSE, but something is clearly amiss. I'm attaching my autoyast profile; it's one of the many variations I have been using: with 1 or 2 interfaces, with and without the "modules" part, with and without the routing, etc. Every time I get the same error. I would welcome any help with this; I found a previous mention of something that looks the same problem at http://lists.suse.com/archive/suse-autoinstall/2005-Jan/0104.html , but, alas, no solution. Best regards, Frederico Muñoz PS: For future reference, are all the fields (network, broadcast...) in the profile required or can I assume that with the IP address and the netmaks the other values will be extrapolated?

1 0

RE: [suse-autoinstall] Selecting packages for autoinstall
by Veenbaas, Pete 16 Sep '05

16 Sep '05

Greetings, I figured out that I must have removed the CORE CD1 dir as well as the SLES 9 CD1 dir. Now I've got the multiple choice back. I would still like to know how the Autoinstall session knows what type of config file to create (e.g. nld9 vs. sles9) when selecting something like 'default system' Thx in advance!!! -----Original Message----- From: Veenbaas, Pete [mailto:pveenbaa@ugs.com] Sent: Friday, September 16, 2005 10:43 AM To: suse-autoinstall(a)suse.com Subject: [suse-autoinstall] Selecting packages for autoinstall Greetings, I currently have an SLE9 32 bit server running as my install server for various flavors of SuSE. I have the following 'enabled' install sources: syslinux3:/suse9 # /usr/bin/installation_sources -s Installation Sources: SUSE SLES 9 Service-Pack Version 1 (http://syslinux3//suse9/sles9_amd64/SUSE-SLES-9-Service-Pack-Version-1/ CD1) SUSE SLES Version 9 (http://syslinux3//suse9/sles9_amd64) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9_32 <http://syslinux3/suse9/nld9_32> ) When I run 'yast2':'Misc':'Autoinstallation' and then select 'Software':'Package Selection' from the configuration tree I see that no base/add-on/individual selected packages are selected. I then click the 'configure' button, and in the 'software' box where I would expect to see: Minimum Minimum graphical system No KDE) Full intallation Default system I see only GNOME KDE What happened to my previous choices? How does autoinstall know which type of config file to create if I want to install a default system for SLES9 SP1 vs. NLD9? Does it know? Any help would be appreciated!

1 0

Selecting packages for autoinstall
by Veenbaas, Pete 16 Sep '05

16 Sep '05

Greetings, I currently have an SLE9 32 bit server running as my install server for various flavors of SuSE. I have the following 'enabled' install sources: syslinux3:/suse9 # /usr/bin/installation_sources -s Installation Sources: SUSE SLES 9 Service-Pack Version 1 (http://syslinux3//suse9/sles9_amd64/SUSE-SLES-9-Service-Pack-Version-1/ CD1) SUSE SLES Version 9 (http://syslinux3//suse9/sles9_amd64) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9) Novell Linux Desktop Version 9 (http://syslinux3//suse9/nld9_32 <http://syslinux3/suse9/nld9_32> ) When I run 'yast2':'Misc':'Autoinstallation' and then select 'Software':'Package Selection' from the configuration tree I see that no base/add-on/individual selected packages are selected. I then click the 'configure' button, and in the 'software' box where I would expect to see: Minimum Minimum graphical system No KDE) Full intallation Default system I see only GNOME KDE What happened to my previous choices? How does autoinstall know which type of config file to create if I want to install a default system for SLES9 SP1 vs. NLD9? Does it know? Any help would be appreciated!

1 0

The service that wouldn't die [powersaved on 9.3 pro]
by Marlier, Ian 16 Sep '05

16 Sep '05

Building an autoinstall for SuSE 9.3 Professional. I really don't want powersaved to run. I have tried both of the following to try to keep it from becoming active: <service> <service_name>powersaved</service_name> </service> and <service> <service_name>powersaved</service_name> <service_status>disable</service_status> </service> Yes, I can add a post-script like chkconfig powersaved off /etc/init.d/powersaved stop and that'll do the trick. But I feel like it shouldn't need to go into a script.. Format 2 -- with service_status = disable -- has always worked in the past. But it doesn't work with this one particular service. Anyone have any idea why? What am I missing? Thanks, Ian

1 0

selecting package architecture
by Jeromy Smith 15 Sep '05

15 Sep '05

Is there any way to specify 32-bit vs 64-bit when selecting software packages? I am installing a 64-bit system but I would like to install the 32-bit gsl libraries (gsl-1.5-3.i586.rpm). It seems like a pretty simple thing but I can't figure it out. Jeromy __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

2 1

rules.xml and <memsize> parameter
by Reynold L Demarco 15 Sep '05

15 Sep '05

I am unable to get my memsize rules working properly. It states in the documentation that the memsize is recognized in megabytes, but that doesn't seem to be the case. Every value I use for memsize seems to match any system, until I get to 10000000000000000000 or greater. In other words, with the below rules.xml, the first rule matches all systems(which is what I want so that every system uses the default.xml file). However, all systems match the next two rules as well, so that all 3 xml files are merged. But I only want the first rule file and one of the 2 next rules files merged based on memory being either less than 3000MB or greater than 3000MB. So I end up getting a merged rules file of all 3. I copied the syntax directly from the example in the autoyast guide. Is there a bug in the memsize option? I am using the below rules.xml file..... <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <memsize> <match>128</match> <match_type>greater</match_type> </memsize> <result> <profile>default.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <result> <profile>cciss.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>3000</match> <match_type>greater</match_type> </memsize> <result> <profile>cciss4g.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <disksize> <match>/dev/cciss/c0d0 1000</match> <match_type>greater</match_type> </disksize> <memsize> <match>5000</match> <match_type>greater</match_type> </memsize> <result> <profile>cciss6g.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> </rules> </autoinstall>

3 16

Re: [suse-autoinstall] rules.xml and <memsize> parameter
by Reynold L Demarco 15 Sep '05

15 Sep '05

I do want default.xml to match all the time, that is done on purpose. It contains all of my default settings. The others match on specific things like memory amounts and disk size. The rules.xml is actually just a test case I ran. My real rules file is much larger. Thx, Renny Michael Marion wrote: >On 13 Sep, Reynold L Demarco wrote: > >I've read the other replies, but I think your logic is backwards anyway. > >The rules and xml files are done in order, IME, and so you'll get default.xml >every time even if the other rules are matched or not, and the result is an >accumulation of all the files that match. I use this to match a site value >for site specific software/scripts and disk sizes for partitioning. > >I think you need to change your rules so that the default one is the last one >so only things that never match above will even try it, and set the other >rules to continue=false so that they don't keep trying to match each other >value.. and check from higher values to lower, or you'll match the first one >that's valid. > >Then there's the problem of the nested rules the other reply mentioned but >that's another issue. > >So I'd redo the rules as: > ><?xml version="1.0"?> ><!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd"> ><autoinstall xmlns="http://www.suse.com/1.0/yast2ns" >xmlns:config="http://www.suse.com/1.0/configns"> ><rules config:type="list"> > <rule> > <disksize> > <match>/dev/cciss/c0d0 1000</match> > <match_type>greater</match_type> > </disksize> > <memsize> > <match>5000</match> > <match_type>greater</match_type> > </memsize> > <result> > <profile>cciss6g.xml</profile> > <continue config:type="boolean">false</continue> > </result> > </rule> > <rule> > <disksize> > <match>/dev/cciss/c0d0 1000</match> > <match_type>greater</match_type> > </disksize> > <memsize> > <match>3000</match> > <match_type>greater</match_type> > </memsize> > <result> > <profile>cciss4g.xml</profile> > <continue config:type="boolean">false</continue> > </result> > </rule> > <rule> > <disksize> > <match>/dev/cciss/c0d0 1000</match> > <match_type>greater</match_type> > </disksize> > <result> > <profile>cciss.xml</profile> > <continue config:type="boolean">true</continue> > </result> > </rule> > <rule> > <memsize> > <match>128</match> > <match_type>greater</match_type> > </memsize> > <result> > <profile>default.xml</profile> > <continue config:type="boolean">true</continue> > </result> > </rule> ></rules> ></autoinstall> > > >Not sure if the cciss.xml one should continue or not. > >I'd suggest doing like I did and breaking up the memory and disk sizes to >completely different rules and xml files anyway. > > >

1 0

How do we implement rules.xml in SELS 8.0
by Jayesh Patel 15 Sep '05

15 Sep '05

HI, I need help on setting the rules.xml setup for our SLES 8 machines. Any alternative for rules.xml will be useful, even if it requires scripting. The thought here is depending on the disk being ide (hda), scsi (sda) or other (c0t0d0) I need to supply the proper autoinstall.xml file. Has any one done a similar setup? Thanks, Jayesh Patel.

2 1

Package selection with autoyast on SuSE 9.3 prof.
by Ian Grant 14 Sep '05

14 Sep '05

I am having a frustrating time here. If I use the autoinstallation option of yast2 to generate an autoyast specification I get a software section like this: <software> <addons config:type="list"> <addon>Basis-Devel</addon> <addon>Basis-Sound</addon> <addon>Kde-Desktop</addon> <addon>Latex</addon> <addon>Min</addon> <addon>Office</addon> <addon>SuSE-Documentation</addon> <addon>X11</addon> </addons> <base>Minimal</base> <packages config:type="list"> <package>autofs</package> <package>lprng</package> </packages> </software> But if I put that in an otherwise working install specification (i.e. with all the other stuff like keyboards, network, X1 config etc.) then, when autoyast halts for me to confirm installation, the 'Software' section of the 'Installation Settings' screen of YaST sows two bullets: The first is '?' and the second is 'Size of packages to install 158.4 MB' and when I go in to the 'Software Selection' screen, I get no base specification shown (i.e. all radio buttons are un-checked) and the list of selected packages under 'Detailed Selection' is blank. If I go ahead with the install it fails trying to install lvm2 because the sed package is missing. Consistent with no base packages being loaded. Does anyone have an example of a working autoyast software specification .xml file for 9.3? I'm using the version of autoyast on the distributed CDs which is 2.11.13-3

3 7

RE: [suse-autoinstall] Package selection with autoyast on SuSE 9.3 prof.
by Marlier, Ian 13 Sep '05

13 Sep '05

I'm just not using the "<addon>" section -- just adding the additional packages that I want as additional <package> lines. That seems to work fine. > -----Original Message----- > From: ig206(a)hermes.cam.ac.uk [mailto:ig206@hermes.cam.ac.uk] On Behalf Of > Ian Grant > Sent: Tuesday, September 13, 2005 10:54 AM > To: suse-autoinstall(a)suse.com > Subject: [suse-autoinstall] Package selection with autoyast on SuSE 9.3 > prof. > > I am having a frustrating time here. If I use the autoinstallation > option of yast2 to generate an autoyast specification I get a > software section like this: > > <software> > <addons config:type="list"> > <addon>Basis-Devel</addon> > <addon>Basis-Sound</addon> > <addon>Kde-Desktop</addon> > <addon>Latex</addon> > <addon>Min</addon> > <addon>Office</addon> > <addon>SuSE-Documentation</addon> > <addon>X11</addon> > </addons> > <base>Minimal</base> > <packages config:type="list"> > <package>autofs</package> > <package>lprng</package> > </packages> > </software> > > But if I put that in an otherwise working install specification (i.e. > with all the other stuff like keyboards, network, X1 config etc.) > then, when autoyast halts for me to confirm installation, the > 'Software' section of the 'Installation Settings' screen of YaST sows > two bullets: The first is '?' and the second is 'Size of packages to > install 158.4 MB' and when I go in to the 'Software Selection' > screen, I get no base specification shown (i.e. all radio buttons are > un-checked) and the list of selected packages under 'Detailed > Selection' is blank. If I go ahead with the install it fails trying > to install lvm2 because the sed package is missing. Consistent with > no base packages being loaded. > > Does anyone have an example of a working autoyast software > specification .xml file for 9.3? I'm using the version of autoyast on > the distributed CDs which is 2.11.13-3 > > > > > -- > To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com > For additional commands, e-mail: suse-autoinstall-help(a)suse.com >

1 0