August 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Bad grub menu after autoyast install
by Eric Rothweiler 27 Aug '10

27 Aug '10

We use a pretty simple AutoYast that simply lays down the same basic install and partitioning using ASK only to pick up IP (address, mask, & gateway) and HOSTNAME info. We come back afterwards to install OES2 on top of SLES. We started this with OES2 (no SP) and have just finally started new installs of OES2 SP2 (SLES 10 SP3). One thing that has been consistent in SP2 and, unfortunately, now SP3 is the grub menu referencing the kernel from one SP earlier. For example, 2.6.16.60-0.21 is now being referenced in the SP3 grub menu after AutoYast installation (the installed kernel is 0.54.5). It doesn't do this every time and I have been unable to find a pattern to the problem appearing. Hoping someone knows why it would be doing this. However, I am willing to do a workaround on this but I'm not a coder by nature and have hit roadblocks figuring out how to include AutoYast code to copy a "standard" grub menu from my install DVD. If anyone could point me to the way to insert this type of code into my AutoYast I would be content. Thanks! Eric -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] SLES 11 SP1 x86_64 invalid root filesystem after autoyast install
by justin.kinney＠academy.com 23 Aug '10

23 Aug '10

Hello all, I'm having a strange problem while trying to use the same autoyast I used for SLES 11 on SLES 11 SP1. I didn't think there would be any compatibility issues, but maybe there is? The problem is that during the second stage of install, after the first reboot, the boot process stops (while still in initrd) and drops me to a shell. When I exit the shell (control-D), the boot process continues and everything is fine. The system functions completely normally after boot. I've engaged Novell support, but so far we have not found a resolution. However, I followed the suggestion of manually installing a machine and then using the cloned autoinst.xml as a starting point. Every time I build a box with that autoyast file, I do not see this issue. I've looked and looked, but cannot find the issue, or any significant difference between my autoyast and the cloned system's autoyast. I've attached both here. Can anybody see something I'm overlooking? There are two files below. The first (autoinst.xml) is a clone of the manually installed system which always works. The second (autoyast_slspgen06e.xml) is the slightly modified SLES 11 autoyast file that produces the invalid root filesystem problem. Also a few screenshots (edited to include an index dot): Thanks in advance, Justin

2 5

[opensuse-autoinstall] AutoYaST goes Twitter
by Uwe Gansert 21 Aug '10

21 Aug '10

Hi, well, it's not that it can read XML files from a twitter feed now ;) but after the blog(*), starting from today, AutoYaST goes one further step to web 2.0 and has it's own twitter account (**). It's not for great hints or enhanced support or so. It's just a little look behind the curtain of my life with AutoYaST ... for those who care ;) And it seems you can't do any bigger project these days without something like a blog, twitter or facebook or ... so ... here it is. (*) http://ugansert.blogspot.com (**) http://twitter.com/autoyast 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 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] vlan boot
by Dirk.Lohmann＠Bertelsmann.de 20 Aug '10

20 Aug '10

Hell, we have got a brand new network Infrastructur it called ngd. Now we have to configure the boot cd with vlan support. We break the installation process and setup the network with the tool vconfig Is it possible to do that automatically ? perhaps with a command in boot options ? Dirk Lohmann -- 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] SLES11 SP1 problems
by Peter Bowen 20 Aug '10

20 Aug '10

I'm attempting to build an AutoYaST install for SLES11 SP1 on x86_64, using the attached file. I've run into several things that are stumping me: 1) It claims to not validate because of the write_hostname element. This element is in the RelaxNG compact syntax files (rnc/*.rnc) but not in the regular RelaxNG files (rng/*.rng). Is it valid? 2) The add-on is not working. It works fine if I manually add it via the URL, but putting in the file results in it not being used. 3) I cannot figure out how to disable kdump. Is there a way? 4) Is there a setting in the XML to disable IPv6? Thanks, Peter

2 4

[opensuse-autoinstall] Dom0 installation autoyast.xml
by Simon Loewenthal 19 Aug '10

19 Aug '10

Dear all, I have several autoyast.xml files that install standard kernels, but I have to create on for a Xen Dom0 (as in the server that manages many other virtualised Xen environments, which sits above the hypervisor - I get confused...). I would like to know which packages I have to add and how I can ensure the installation adds the correct Xen kernel? Here is what I have so far: ** PACKAGES <patterns config:type="list"> <pattern>Minimal</pattern> <pattern>apparmor</pattern> <pattern>base</pattern> <pattern>documentation</pattern> <pattern>file_server</pattern> <pattern>xen_server</pattern> </patterns> <packages> <package>kernel-xen-base</package> <package>xen-libs</package> <package>xen-tools-domU</package> <package>xen-tools</package> <package>xen</package> </packages> ** GRUB Grub entry currently has this, which should be changed to the Xen kernel, but I not know what I should add: <loader_type>grub</loader_type> <sections config:type="list"> <section> <append>resume=/dev/system/swap splash=silent crashkernel=256M-:128M@16M showopts</append> <image>/boot/vmlinuz-2.6.27.19-5-default</image> <initial>1</initial> <initrd>/boot/initrd-2.6.27.19-5-default</initrd> <lines_cache_id>0</lines_cache_id> <name>SUSE Linux Enterprise Server 11 - 2.6.27.19-5</name> <original_name>linux</original_name> <root>/dev/system/root</root> <type>image</type> [SNIP] ** KERNEL There are these packages that could be added, but I am unsure which one should add the correct kernel for the DomU: ../sles11-dvd1-x86_64/boot/x86_64/initrd-xen ../sles11-dvd1-x86_64/boot/x86_64/vmlinuz-xen ../sles11-dvd1-x86_64/suse/x86_64/kernel-xen-base-2.6.27.19-5.1.x86_64.rpm ../sles11-dvd1-x86_64/suse/x86_64/kernel-xen-2.6.27.19-5.1.x86_64.rpm ../sles11-dvd1-x86_64/suse/x86_64/kernel-xen-base-2.6.27.19-5.1.x86_64.rpm ../sles11-dvd1-x86_64/suse/setup/descr/xen_server-32bit-11-38.5.x86_64.pat.gz ../sles11-dvd1-x86_64/suse/setup/descr/xen_server-11-38.5.x86_64.pat.gz I suspect that I add one of these as a package, and then change the Grub entry above to reflect the correct Dom0 kernel, but again I am unsure what ought to be what. Anyone shed a little bit of light on this? Best regards, z. PS. I don't have the luxery of booting off a DVD and then cloning the resulting system into an autoyast.xml because the DVD is via a virtual Java applet from an HP Onboard Administrator; My Java installation is broken somewhere and the Java applet fails. This is why not, in case someone asks. -- 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] Download failed: /repotada/repomd.xml - [AbstractCommand.cc224]
by Ivan De Masi 19 Aug '10

19 Aug '10

Hello again, after the first reboot (stage2) I get the following message: Download failed: /repotada/repomd.xml [AbstractCommand.cc224] URI=http://download.opensuse.org/update/11.2/repodata/repomd.xml I found out that this happens because of the misconfigured network device. The network devive is always regogniced as "eth1" after the reboot instead of "eth0". My network config looks like this: <networking> <dhcp_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> <domain>asta.tu-darmstadt.de</domain> <hostname>test</hostname> <resolv_conf_policy>auto</resolv_conf_policy> <searchlist config:type="list"> <search>asta.tu-darmstadt.de</search> </searchlist> </dns> <interfaces config:type="list"> <interface> <bootproto>dhcp4</bootproto> <device>eth0</device> <startmode>auto</startmode> </interface> </interfaces> <managed config:type="boolean">false</managed> <net-udev config:type="list"> <rule> <name>eth0</name> <rule>ATTR{address}</rule> <value></value> </rule> </net-udev> <routing> <ip_forward config:type="boolean">false</ip_forward> </routing> </networking> What's wrong with this? Thanks! Regards, Ivan -- AStA TU Darmstadt IT-Administration Hochschulstr. 1 64289 Darmstadt University of Technology Darmstadt Tel. +49-6151-162217 Fax. +49-6151-166026 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4

[opensuse-autoinstall] autoyast and updates repository
by Pierre Girard 11 Aug '10

11 Aug '10

Hello, in opensuse 11.1 we had the update repository in autoyast and after the installation, the existing updates were already applied. In 11.2 we got an error message during the installation and 11.3 seems to be doing the same. Any idea how to set up an update repo in autoyast or is this no longer possible? I don't think it makes any difference but we rsync rsync://rsync.opensuse.org/opensuse-full/opensuse/ so we have a local copy of the files needed for installation and updates and we do the install over NFS. I was just adding something like: <listentry> <media_url><![CDATA[nfs://nfs.example.com/suse/opensuse/update/11.3]]></media_url> <product>local updates</product> <product_dir>/</product_dir> </listentry> I was also wondering if there's a way to configure automatic updates from that repo, maybe once a week. Thanks for your help. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 5

[opensuse-autoinstall] unsubscribe
by Guido Kölsch 10 Aug '10

10 Aug '10

-- 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] Where can I see y2log ?
by Ivan De Masi 06 Aug '10

06 Aug '10

Hello, I'm trying to create new autoyast config files and when an installations fails the output is poor. Where can I get the y2log of autoyast to see in deep what's happening? Do I have to access the disk of the machine I tried to install or is it somewhere in "memory"? Thanks! Regards, Ivan -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4