August 2006 - openSUSE Autoinstall - openSUSE Mailing Lists

"No products to register" after autoyast installation
by Jan Steinkuehler (AC/EDD) 25 Aug '06

25 Aug '06

Hey, After an autoyast installation registration of the system (and hence automaticupdates) fail. blade5-eth0:~ # suse_register No products to register blade5-eth0:~ # ls /var/lib/zypp/db/products blade5-eth0:~ # We used our own installation source (copy from the DVDs) but we nerver had these problem in a manual installation. Any ideas? (Is there a default location for the autoyast-logfile? Does someone want to have a look at it?) Regards Jan -- Autoyast config file follows: <?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"> <bootloader> <activate config:type="boolean">true</activate> <global> <embed_stage1.5 config:type="boolean">true</embed_stage1.5> <lines_cache_id>0</lines_cache_id> <prompt>1</prompt> <stage1_dev>/dev/sda1</stage1_dev> <timeout config:type="integer">8</timeout> </global> <initrd_modules config:type="list"> <initrd_module> <module>amd74xx</module> </initrd_module> <initrd_module> <module>cciss</module> </initrd_module> <initrd_module> <module>qla2xxx</module> </initrd_module> <initrd_module> <module>processor</module> </initrd_module> <initrd_module> <module>thermal</module> </initrd_module> <initrd_module> <module>fan</module> </initrd_module> <initrd_module> <module>reiserfs</module> </initrd_module> </initrd_modules> <loader_device></loader_device> <loader_type>grub</loader_type> <location>mbr</location> <repl_mbr config:type="boolean">false</repl_mbr> <sections config:type="list"> <section> <append>resume=/dev/sda2 splash=silent showopts</append> <initial>1</initial> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>1</lines_cache_id> <name>SUSE Linux 10.1</name> <original_name>linux</original_name> <root>/dev/sda1</root> <type>image</type> </section> <section> <append>showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0 edd=off 3</append> <initrd>/boot/initrd</initrd> <kernel>/boot/vmlinuz</kernel> <lines_cache_id>2</lines_cache_id> <name>Failsafe -- SUSE Linux 10.1</name> <original_name>failsafe</original_name> <root>/dev/sda1</root> <type>image</type> </section> <section> <append>resume=/dev/sda2 splash=silent showopts</append> <initrd>/boot/initrd-xen</initrd> <kernel>/boot/vmlinuz-xen</kernel> <lines_cache_id>3</lines_cache_id> <name>Xen -- </name> <original_name>Xen -- </original_name> <root>/dev/sda1</root> <type>image</type> <xen>/boot/xen.gz</xen> <xen_append></xen_append> </section> </sections> </bootloader> <general> <mode> <confirm config:type="boolean">false</confirm> </mode> <mouse> <id>none</id> </mouse> <signature-handling/> </general> <groups config:type="list"/> <networking> <dhcp_options> <dhclient_additional_options></dhclient_additional_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">true</dhcp_hostname> <dhcp_resolv config:type="boolean">true</dhcp_resolv> <domain>site</domain> <hostname>linux-uqg5</hostname> <nameservers config:type="list"> <nameserver>192.168.16.254</nameserver> <nameserver>212.117.68.10</nameserver> <nameserver>212.117.64.86</nameserver> </nameservers> <searchlist config:type="list"> <search>mwrl.net</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>eth-id-00:14:c2:3d:2c:a2</device> <name>Compaq NC7782 Gigabit Server Adapter (PCI-X, 10,100,1000-T)</name> <netmask>255.255.255.0</netmask> <startmode>auto</startmode> <usercontrol>no</usercontrol> </interface> </interfaces> <managed config:type="boolean">false</managed> <modules config:type="list"> <module_entry> <device>bus-pci-0000:02:02.0</device> <module>tg3</module> <options></options> </module_entry> </modules> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> <nfs config:type="list"> <nfs_entry> <mount_point>/home</mount_point> <nfs_options>defaults</nfs_options> <server_path>guam:/home</server_path> </nfs_entry> <nfs_entry> <mount_point>/data</mount_point> <nfs_options>defaults</nfs_options> <server_path>blade6:/mnt/san_v17</server_path> </nfs_entry> </nfs> <nis> <nis_broadcast config:type="boolean">false</nis_broadcast> <nis_broken_server config:type="boolean">false</nis_broken_server> <nis_by_dhcp config:type="boolean">false</nis_by_dhcp> <nis_domain>research.lab</nis_domain> <nis_local_only config:type="boolean">false</nis_local_only> <nis_options></nis_options> <nis_other_domains config:type="list"/> <nis_servers config:type="list"> <nis_server>guam</nis_server> </nis_servers> <start_autofs config:type="boolean">false</start_autofs> <start_nis config:type="boolean">true</start_nis> </nis> <online_update> <autoget config:type="boolean">false</autoget> <enable_autoupdate config:type="boolean">true</enable_autoupdate> <skipPre config:type="boolean">true</skipPre> <update_time> <day config:type="integer">0</day> <hour config:type="integer">0</hour> <minute config:type="integer">0</minute> <random_time config:type="boolean">true</random_time> <timing>weekly</timing> </update_time> </online_update> <partitioning config:type="list"> <drive> <device>/dev/sda</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">reiser</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <size>7304015872</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <size>1077511168</size> </partition> </partitions> <use>all</use> </drive> </partitioning> <report> <errors> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </errors> <messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </messages> <warnings> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </warnings> <yesno_messages> <log config:type="boolean">true</log> <show config:type="boolean">true</show> <timeout config:type="integer">0</timeout> </yesno_messages> </report> <runlevel> <default>3</default> </runlevel> <software> <addons config:type="list"> <addon>X11</addon> <addon>Min</addon> </addons> <base>Minimal+X11</base> <packages config:type="list"> <package>yast2-trans-en_US</package> (...) <package>xen</package> </packages> </software> <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">false</encrypted> <user_password>(..)</user_password> <username>root</username> </user> </users> </profile> -- Jan Steinkuehler Ericsson Research Ericsson GmbH, Eurolab EDD/XR/N Ericsson Allee 1 D-52134 Herzogenrath jan.steinkuehler(a)ericsson.com

1 0

RE: [suse-autoinstall] current DTD
by Paul DiSciascio 24 Aug '06

24 Aug '06

Ok, well, is the <configure/> element still valid in SLES 10? Some of the documentation has it; some doesn't; and the autoinst.xml file that the autoyast control panel applet generated does not have it. ~Paul -----Original Message----- From: Uwe Gansert [mailto:ug@suse.de] Sent: Thursday, August 24, 2006 3:20 AM To: suse-autoinstall(a)suse.com Subject: Re: [suse-autoinstall] current DTD On Wednesday 23 August 2006 17:40, Paul DiSciascio wrote: > I'm using SLES10 and I am trying to validate autoinst.xml against the > dtd that installed in /usr/share/autoinstall/dtd/profile.dtd and > finding this quite difficult because the DTD doesnt seem to be > current. (e.g. it doesnt include any of the signature-handling > elements). > > Does anyone know where I can get an up-to-date DTD? there is none at the moment - sorry for that. -- ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, Maxfeldstrasse 5, D-90409 Nuernberg, Germany Business: http://www.suse.de/~ug now playing Agonoize - Sacrilege -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

2 1

Can't save packet selection in 10.1???
by Frank Steiner 24 Aug '06

24 Aug '06

Hi, where's the feature to save/export a package selection gone in 10.1??? I'm trying to create our own .sel file, but I've no idea how to do that if I cannot save the selection that I create in the software selection menu of autoyast. How am I supposed to create my own selection file, mentioned in section "4.5.3. Custom Package Selections"? Has this feature vanished, once again? cu, Frank -- Dipl.-Inform. Frank Steiner Web: http://www.bio.ifi.lmu.de/~steiner/ Lehrstuhl f. Bioinformatik Mail: http://www.bio.ifi.lmu.de/~steiner/m/ LMU, Amalienstr. 17 Phone: +49 89 2180-4049 80333 Muenchen, Germany Fax: +49 89 2180-99-4049 * Rekursion kann man erst verstehen, wenn man Rekursion verstanden hat. *

3 4

current DTD
by Paul DiSciascio 24 Aug '06

24 Aug '06

I'm using SLES10 and I am trying to validate autoinst.xml against the dtd that installed in /usr/share/autoinstall/dtd/profile.dtd and finding this quite difficult because the DTD doesnt seem to be current. (e.g. it doesnt include any of the signature-handling elements). Does anyone know where I can get an up-to-date DTD? Thanks, Paul

2 1

Re: [suse-autoinstall] Installing multiple sites with one CD/DVD
by aschanz＠lcsc.dfs.de 24 Aug '06

24 Aug '06

Maybe you could add the parameter <args> to the script block in AutoYast. We could then modify this parameter with the result of the question. Example: <script> <debug config:type="boolean">true</debug> <args> put arguments for script here</args> <feedback config:type="boolean">false</feedback> <filename>lcsc-config</filename> <interpreter>shell</interpreter> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[ ... ]]></source> </script> ask part: <ask> <path>post-scripts,lcsc-config,args</path> <question>Site</question> <type>symbol</type> <selection config:type="list"> <entry> <value config:type="symbol">Site1</value> <label>Site One installation Options</label> </entry> <entry> <value config:type="symbol">Site2</value> <label>site two installation Options</label> </entry> </selection> </ask> This would be a very smart solution which could be useful for many users. Regards, Alexander Alexander Schanz DFS Deutsche Flugsicherung GmbH Head of Linux Competence and Service Center

2 1

Installing multiple sites with one CD/DVD
by aschanz＠lcsc.dfs.de 23 Aug '06

23 Aug '06

Hello, we have the following problem and are searching for a solution without writing a yast module. We have to install numerous systems in different locations (Sites). Each site has separate settings and special configurations. We have set up a folder with site specific sub-dirs containing the information. A Special Chroot/init script is processing the site-specific files and configures the system. We do this by providing an option to the kernel like site=xxx. While this is working fine, the customer requested an additional mode where Yast asks for the Site information if the kernel parameter was not specified. The <ask> directive looks promising but we are missing a way to return the selected Site to our script. We cold modify the xml file to contain the available sites with a pre-script but we don't see a way to communicate the selected site back to a script or variable which could be used by a shell script. Is there a way to do something like this without writing a yast module for the task?

2 1

setup RHEL4 server for autoyast?
by Peter Strifas 22 Aug '06

22 Aug '06

I have a RHEL4 AS update3 server setup for kickstart -- can I also setup an install source on this server to install SLES9 SP3 servers (the dhcp server, tftp server is already configured). Would it be as simple as copying the ISOs to a directory and running the a script called 'create_sles9_instdir.sh' (see attached)? Is RHEL4 a supported platform for a SLES9 installation source? Thanks in advance for your time and patience. - Peter

2 1

starting online update automatically after autoinstall
by Sebastian Reitenbach 21 Aug '06

21 Aug '06

Hi, I use opensuse 10.1. I got my clients to use PXE boot to find their configuration on the http server and to start installation process. Do I can make an automated online update, add a rpm source and run rug? Is that possible to configure from within autoyast or do I have to start that process from within custom scripts after the standard installation is ready? any hints or links to documentation are welcome. kind regards Sebastian

1 0

SLES 10: more than one primary partition?
by Holger Reif 21 Aug '06

21 Aug '06

Hi, I'm trying to use the partition scheme that used for partitioning SLES8 and SLES9 systems. The minimal autoinst.xml snippet looks like <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">VAR_boot_filesystem</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">1</partition_nr> <size>96M</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <partition_nr config:type="integer">5</partition_nr> <size>8192M</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <mount>/</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <size>max</size> </partition> </partitions> <use>all</use> </drive> What I expect is: 1st primary 96M /boot 2nd primary some 130G / 1st logical 6G swap What I get is: / # fdisk -l Disk /dev/cciss/c0d0: 146.8 GB, 146807930880 bytes 255 heads, 63 sectors/track, 17848 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/cciss/c0d0p1 1 13 104391 83 Linux /dev/cciss/c0d0p2 14 17848 143259637+ f W95 Ext'd (LBA) /dev/cciss/c0d0p5 14 16803 134865643+ 83 Linux /dev/cciss/c0d0p6 16804 17848 8393931 82 Linux swap / Solaris BTW. If I do not specify partition_id and partition_nr for swap then root get's first logical partion and swap second one. Is there any chance to force / to be a primary partition w/o using part.info? http://www.suse.de/~ug/autoyast_doc/CreateProfile.Partitioning.html#id25297… sugests that my snippet should do what I want... br Holger Reif -- Echte DSL-Flatrate dauerhaft für 0,- Euro*. Nur noch kurze Zeit! "Feel free" mit GMX DSL: http://www.gmx.net/de/go/dsl

2 2

yast crashes while editing config-file
by Daniel Spannbauer 18 Aug '06

18 Aug '06

Hello, I try to edit a Config.xml-File with the Autoyast-Module of Yast in SuSEe 10.1. This config.xml-Modul was edited with kxmleditor cause there was no config for for the User in it. Find attached the y2log of this. Any hints to solve this? A have to do some changes in the Package-Selection. Regards Daniel

3 2