October 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] yast2 <module> commandline with no tty
by Lars Stavholm 25 Oct '10

25 Oct '10

Hi All, I'm trying to run yast2 for a specific module in an init-script, but yast2 complains about the lack of tty. Does anyone now how to get around this? One of the commands I'm trying to run is: yast2 ldap-server service verbose enable Any input appreciated. /Lars Stavholm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Signature Check Failed
by Bart Wahlgren 20 Oct '10

20 Oct '10

This is probably not a AutoYast issue but I thought I'd see if someone on the mailing list knows what is causing this. I'm attempting to create a custom install DVD of SLED 11.0 using Product Creator in Yast. After burning the ISO to disk and attempting an installation the following error comes up. Cd:/content: signature check failed. It comes up way before the autoinst.xml file is accessed and occurs if I select manual or autoinstall from the GRUB menu. Thanks Bart Wahlgren Network Administrator Speed Script Pharmacy Systems Direct: 913-643-2454 Fax: 913-894-1802 bwahlgren(a)speedscript.com www.speedscript.com The Speed Script difference --> www.speedscript.com/impactmovie Speed Script is a registered trademark of Digital Simplistics, Inc. This electronic message, including any attachments, may contain confidential or privileged information and is intended for the individual or entity named above. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. If you have received this electronic transmission in error, please notify the sender immediately and destroy all electronic and hard copies of the communication, including attachments. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Problems with ay 11.3 images
by 686f6c6d 19 Oct '10

19 Oct '10

Regarding http://ugansert.blogspot.com/2010/09/autoyast-and-image-creationinstallatio…, first I (sometimes) had the problem that when adding software, I was not asked for the DVD (as mentioned on twitter yesterday). Starting autoyast again and entering the software selection fixed that. Now I always get this error message somewhere after "Compressing the image": Error ISO creation failed in '/tmp/ay_iso/'. Please check /tmp/ay_image.log The log contains within its tiny 33000 lines the following errors (I may very well have overlooked some, given that I have no idea what to look for): ---------- 8< ---------- [...] Retrieving package master-boot-code-1.22-1.6.i586 (139/294), 8.0 KiB (9.0 KiB unpacked) Installing: master-boot-code-1.22-1.6 [.done] Retrieving package libblocxx6-2.1.0.342-136.1.x86_64 (140/294), 334.0 KiB (1.1 MiB unpacked) Installing: libblocxx6-2.1.0.342-136.1 [.done] Retrieving package perl-RPC-XML-0.67-6.1.x86_64 (141/294), 168.0 KiB (491.0 KiB unpacked) Installing: perl-RPC-XML-0.67-6.1 [.done] Retrieving package ca-certificates-1-5.3.noarch (142/294), 16.0 KiB (26.0 KiB unpacked) Installing: ca-certificates-1-5.3 [.done] Additional rpm output: /var/tmp/rpm-tmp.k9WfVE: line 4: rm: command not found Updating certificates in /etc/ssl/certs... 0 added, 0 removed. creating /var/lib/ca-certificates/ca-bundle.pem ... /usr/lib/ca-certificates/update.d/certbundle.run: line 21: cat: command not found /usr/lib/ca-certificates/update.d/certbundle.run: line 39: mv: command not found /usr/lib/ca-certificates/update.d/java.run: line 38: which: command not found /usr/lib/ca-certificates/update.d/java.run: line 17: rm: command not found Retrieving package apparmor-docs-2.3.1-21.1.noarch (143/294), 258.0 KiB (393.0 KiB unpacked) Installing: apparmor-docs-2.3.1-21.1 [.done] [...] Retrieving package lcms-1.18a-8.1.x86_64 (155/294), 48.0 KiB (160.0 KiB unpacked) Installing: lcms-1.18a-8.1 [.done] Retrieving package ca-certificates-mozilla-1.62-2.3.noarch (156/294), 115.0 KiB (198.0 KiB unpacked) Installing: ca-certificates-mozilla-1.62-2.3 [.done] Additional rpm output: Updating certificates in /etc/ssl/certs... 121 added, 0 removed. creating /var/lib/ca-certificates/ca-bundle.pem ... /usr/lib/ca-certificates/update.d/certbundle.run: line 21: cat: command not found /usr/lib/ca-certificates/update.d/certbundle.run: line 39: mv: command not found /usr/lib/ca-certificates/update.d/java.run: line 38: which: command not found /usr/lib/ca-certificates/update.d/java.run: line 17: rm: command not found Retrieving package yast2-core-2.19.2-3.1.x86_64 (157/294), 936.0 KiB (3.3 MiB unpacked) Installing: yast2-core-2.19.2-3.1 [.done] [...] Retrieving package limal-ca-mgm-1.6.4-1.6.x86_64 (180/294), 688.0 KiB (3.0 MiB unpacked) Installing: limal-ca-mgm-1.6.4-1.6 [.done] Retrieving package glibc-locale-2.11.2-2.4.x86_64 (181/294), 5.9 MiB (106.1 MiB unpacked) Installing: glibc-locale-2.11.2-2.4 [................done] Retrieving package glib2-2.24.1-2.5.x86_64 (182/294), 181.0 KiB (702.0 KiB unpacked) Installing: glib2-2.24.1-2.5 [.done] Additional rpm output: /usr/bin/gio-querymodules-64: error while loading shared libraries: libgobject-2.0.so.0: cannot open shared object file: No such file or directory warning: %post(glib2-2.24.1-2.5.x86_64) scriptlet failed, exit status 127 Retrieving package gfxboot-4.2.3-2.1.x86_64 (183/294), 22.0 KiB (72.0 KiB unpacked) Installing: gfxboot-4.2.3-2.1 [.done] [...] Retrieving package yast2-transfer-2.18.0-6.2.x86_64 (227/294), 58.0 KiB (314.0 KiB unpacked) Installing: yast2-transfer-2.18.0-6.2 [.done] Retrieving package satsolver-tools-0.15.0-1.21.x86_64 (228/294), 214.0 KiB (1.7 MiB unpacked) Installing: satsolver-tools-0.15.0-1.21 [.done] Retrieving package pam-config-0.73-2.10.x86_64 (229/294), 88.0 KiB (443.0 KiB unpacked) Installing: pam-config-0.73-2.10 [.done] Additional rpm output: WARNING: Couldn't find /etc/security/pam_unix2.conf{.rpmsave} (No such file or directory). WARNING: Couldn't find /etc/security/pam_pwcheck.conf{.rpmsave} (No such file or directory). WARNING: Couldn't load old config files. *** load_obsolete_conf (...) *** load_config (/etc/pam.d/common-account, account, ...) [...] Installing: module-init-tools-3.12-1.3 [.done] Retrieving package grub-0.97-171.1.x86_64 (231/294), 330.0 KiB (1.4 MiB unpacked) Installing: grub-0.97-171.1 [.done] Additional rpm output: 0+1 records in 0+1 records out 102026 bytes (102 kB) copied, 0.000158618 s, 643 MB/s df: Warning: cannot read table of mounted file systems Retrieving package cryptsetup-1.1.2-3.3.x86_64 (232/294), 85.0 KiB (238.0 KiB unpacked) Installing: cryptsetup-1.1.2-3.3 [.done] [...] Retrieving package kernel-default-2.6.34-12.3.x86_64 (2/4), 31.9 MiB (128.1 MiB unpacked) Installing: kernel-default-2.6.34-12.3 [............................done] Additional rpm output: df: Warning: cannot read table of mounted file systems Free diskspace below /boot: 12196880 blocks Please run mkinitrd as soon as your system is complete. You may need to setup and install the boot loader using the available bootloader for your platform (e.g. grub, lilo, zipl, ...). Retrieving package wireless-regdb-2009.11.25-3.1.noarch (3/4), 6.0 KiB (5.0 KiB unpacked) Installing: wireless-regdb-2009.11.25-3.1 [.done] [...] (the file ends with a long list of files:) [...] ./lib/firmware/2.6.34-12-default/tehuti/bdx.bin ./lib/libutil.so.1 ./lib/apparmor/ ./lib/apparmor/rc.apparmor.functions ---------- >8 ---------- How can I fix those errors? Are they important at all? The system I'm trying this on works fine, at least "zypper ve" and the like are not complaining. Thanks for your time, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] LDAP server
by Lars Stavholm 17 Oct '10

17 Oct '10

s it possible to use autoyast to include an LDAP server setup in the installation? /L -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

[stava: Re: [opensuse-autoinstall] bootloader problem]
by Lars Stavholm 15 Oct '10

15 Oct '10

On Tue, Oct 12, 2010 at 12:23:06PM +0200, Uwe Gansert wrote: > on Monday 11 October 2010 Lars Stavholm wrote: > > > I have a bit of a wirdness in OpenSuSE 11.3 autoyast that I need some help > > with. > > that looks like: > https://bugzilla.novell.com/show_bug.cgi?id=626132 It sure does. > Did you install all updates in stage1? Hmm, how do I do that? I have the DVD (bought) and extracted to a 'base' directory, then I download the updates and make them available in another directory 'updates', both of these available for autoyast during autoinstall time. I thought that was good enough. /L > -- > ciao, Uwe Gansert > > Uwe Gansert > SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) > Business: http://www.suse.de/~ug > -- > To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org > For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] using PLDP disk in autoyast installation
by Vladimir Ondrus 14 Oct '10

14 Oct '10

Hi All, My hardware is FSC RX200 S4, i am using SLES10 SP3. FSC offers new drivers as PLDP iso image. http://ts.fujitsu.com/products/standard_servers/linux_readmes_popup.html There is possibility to press F5 during manual installation to load drivers from PLDP iso. But we are doing automatic installation, I export content of PLDP disk via NFS and I include this to autoyast.xml: <add-on> <add_on_products config:type="list"> <listentry> <media_url>nfs://219.1.90.50/pldp_disk</media_url> <product>PRIMERGY_ALL</product> <product_dir>/</product_dir> </listentry> </add_on_products> </add-on> Installation is OK, add-on is succesfully registred, but drivers from PLDP disk are not included in my installed system. Is in autoyast.xml equivalent syntax for manual installation "press F5" ? Regards, Vladimir Ondrus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] bootloader problem
by Lars Stavholm 12 Oct '10

12 Oct '10

Hi all, I have a bit of a wirdness in OpenSuSE 11.3 autoyast that I need some help with. It's the bootloader definitions in /boot/grub/menu.lst that seems to get messed up at some point. My configuration involves LVM and RAID 1 on 3 disks, see relevant autoinst.xml parts below. Now, what happens is that the boot disk partition definition gets messed up in a rather random way. It starts out as being "(hd0,0)", but then along the way, it gets replaced with "(hd0,<garbage>)" where <garbage> becoms a sequence of random digits, e.g. 8 or 28376, or 941 or something completely irrelevant. I've tried to fix this with a simple postpartitioning-script, chroot-script, post-script, and init-script, but there's always one point (I do believe it's the second reboot, i.e. after the chroot-scripts being executed, but before the post-scripts get executed) where the "(hd0,0)" gets clogged up that prevents the boot. I have to enter the grub menu and edit the offendig lines manually. Then, in the installed system, I need to permanent the changes by editing the offending lines again, this time using vi in the running system. The problem manifests itself when using 3 disk setup with RAID 1, but not with 3 disks under LVM without RAID 1. Other than that, everything seems just fine. Any ideas, anyone? R /Lars Stavholm --- Begin Included Message --- [snip] <bootloader> <global> <activate>true</activate> <boot_custom>/dev/md0</boot_custom> <boot_mbr>true</boot_mbr> <generic_mbr>true</generic_mbr> <timeout config:type="integer">5</timeout> </global> <loader_type>grub</loader_type> </bootloader> [snip] <partitioning config:type="list"> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/md</device> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext2</filesystem> <format config:type="boolean">true</format> <mount>/boot</mount> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">0</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> <partition> <lvm_group>sys</lvm_group> <partition_id config:type="integer">142</partition_id> <partition_nr config:type="integer">1</partition_nr> <raid_options> <raid_type>raid1</raid_type> </raid_options> </partition> </partitions> <type config:type="symbol">CT_MD</type> <use>all</use> </drive> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sda</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>100MB</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>100MB</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <initialize config:type="boolean">true</initialize> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">1</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md0</raid_name> <size>100MB</size> </partition> <partition> <partition_id config:type="integer">253</partition_id> <partition_nr config:type="integer">2</partition_nr> <partition_type>primary</partition_type> <raid_name>/dev/md1</raid_name> <size>max</size> </partition> </partitions> <type config:type="symbol">CT_DISK</type> <use>all</use> </drive> <drive> <device>/dev/sys</device> <initialize config:type="boolean">true</initialize> <partitions config:type="list"> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>home</lv_name> <mount>/home</mount> <fstopt>defaults,acl,usrjquota=aquota.user,jqfmt=vfsv0</fstopt> <partition_id config:type="integer">131</partition_id> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">ext3</filesystem> <format config:type="boolean">true</format> <lv_name>root</lv_name> <mount>/</mount> <fstopt>defaults</fstopt> <partition_id config:type="integer">131</partition_id> <size>1GB</size> </partition> <partition> <filesystem config:type="symbol">swap</filesystem> <format config:type="boolean">true</format> <lv_name>swap</lv_name> <fstopt>defaults</fstopt> <mount>swap</mount> <partition_id config:type="integer">130</partition_id> <size>6GB</size> </partition> </partitions> <pesize>4M</pesize> <type config:type="symbol">CT_LVM</type> <use>all</use> </drive> </partitioning> [snip] --- End Included Message --- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

[opensuse-autoinstall] Setting update dhcp with hostname
by Ruediger Gunreben 11 Oct '10

11 Oct '10

Hi, I want to register the hostname of the newly installed system to the dns server. Which options do I have to configure in the autoyast sections? We are using SLES11 unfortunately theses options are not documented very well: ------------------------------------------ <dhcp_options> <dhclient_client_id></dhclient_client_id> <dhclient_hostname_option>AUTO</dhclient_hostname_option> </dhcp_options> <dns> <dhcp_hostname config:type="boolean">false</dhcp_hostname> <domain>isarnet.lab</domain> <hostname>isarflow</hostname> <resolv_conf_policy>auto</resolv_conf_policy> <searchlist config:type="list"> <search>isarnet.lab</search> </searchlist> </dns> ------------------------------------------ Regards Ruediger -- Ruediger Gunreben Tel: +49 811 99829 116 Fax: +49 811 99829 216 GSM: +49 178 7072030 E-Mail: ruediger.gunreben(a)isarnet.de CCIE R+S #21614 ________________________________________ Support IsarFlow Tel.: 0811 99829 270 E-Mail: support(a)isarflow.de IsarNet Software Solution GmbH Terminalstrasse Mitte 18 85356 Muenchen http://www.isarflow.de http://www.isarnet.de ________________________________________ IsarNet AG Terminalstrasse Mitte 18 85356 Muenchen Sitz der Gesellschaft: Oberding Handelsregister Muenchen, HRB 127295 USt.-ID Nr. DE203054669 Vorstand: Andreas Perthel, Harald Weikert Vorsitzender des Aufsichtsrates: Andreas Gallenmueller ________________________________________ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 2

[opensuse-autoinstall] Remastering
by Erico Mendonça 07 Oct '10

07 Oct '10

I have an autoyast-based installation that will soon be going over 4.7GB. What is the easiest way to remaster it into multiple CDs/DVDs? It's SLE-based. Is there a tool to automatically split repos/create the catalogs? Or should I resort to splitting the repos manually and referencing them? -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 4

[opensuse-autoinstall] rules.xml and CIDR networks
by 686f6c6d 07 Oct '10

07 Oct '10

Greetings, we have a lot of CIDR networks. For our /16 and /24 networks, we have no problem at all with <network> or <hostadress> matches, but how does that work for CIDR addresses? We have tried both of the following options, without success: ---------- 8< ---------- <rule> <network> <match>10.11.12.128/27</match>  <match_type>exact</match_type> </network> <result> <profile>base.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> ---------- >8 ---------- >From the server logs, I assume matching does not work (ie. the client is not discovered to be in that network): ---------- 8< ---------- "GET /ay/11.3/rules/rules.xml HTTP/1.1" 200 4200 "GET /ay/11.3/DEADBEEF HTTP/1.1" 404 293 "GET /ay/11.3/DEADBEE HTTP/1.1" 404 292 "GET /ay/11.3/DEADBE HTTP/1.1" 404 291 "GET /ay/11.3/DEADB HTTP/1.1" 404 290 "GET /ay/11.3/DEAD HTTP/1.1" 404 289 "GET /ay/11.3/DEA HTTP/1.1" 404 288 "GET /ay/11.3/DE HTTP/1.1" 404 287 "GET /ay/11.3/D HTTP/1.1" 404 286 "GET /ay/11.3/hexip-uppercase HTTP/1.1" 404 297 "GET /ay/11.3/hexip-lowercase HTTP/1.1" 404 297 "GET /ay/11.3/default HTTP/1.1" 404 292 ---------- >8 ---------- Is this supposed to work? Any help would be greatly appreciated. tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5