- openSUSE Autoinstall

[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

[opensuse-autoinstall] How to set filesystem type
by Henrik Schmidt 05 Aug '10

05 Aug '10

I'm using <partitioning_advanced> and <fstab> with my autoinstall for 11.3, Is it possible to force the filesystem for partitions declared to be formated ? I want them to be ext4 instead of ext3. <partitioning_advanced> <fstab>  <root_partition>/dev/sda2</root_partition> <use_existing_fstab config:type="boolean">true</use_existing_fstab>  <partitions config:type="list"> <partition> <format config:type="boolean">true</format> <mount>swap</mount> <mountby config:type="symbol">id</mountby> </partition> <partition> <format config:type="boolean">true</format> <mount>/</mount> <mountby config:type="symbol">id</mountby> </partition> <partition> <format config:type="boolean">false</format> <mount>/export/opt</mount> <mountby config:type="symbol">id</mountby> </partition> <partition> <format config:type="boolean">false</format> <mount>/export/home</mount> <mountby config:type="symbol">id</mountby> </partition> </partitions> </fstab> </partitioning_advanced> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 3

[opensuse-autoinstall] tool for cleaning up repositories
by Magyari, Miklos 03 Aug '10

03 Aug '10

hi all, I apologize, this is not a real autoyast questions but you may have some pointers for me. We are using autoyast to install different SLED releases. My problem is that for higher SP releases the "updates" repo from Novell grows quite big, most of the packages have several different versions in the repo. For SP3, there are more than 10.000 rpms in updates. What I'm looking for is a script that can help me to find/remove obsolete rpms. Do you know any? thanks, Miki -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

Re: [opensuse-autoinstall] "Invalid partition table" on SLES10SP2/3 with soft RAID
by Andreas Taschner 02 Aug '10

02 Aug '10

Thank you for responding. >>> On 6/17/2010 at 16:39, Uwe Gansert <ug(a)suse.de> wrote: > on Thursday 17 June 2010 Andreas Taschner wrote: > >> I am trying to duplicate a problem at a customer that has a RAID1 setup >> with /boot, / and other partitions on md. For this I install SLES10SP2 as >> step one and upgrade to SLES10SP3 as step2. Doing this manually works >> fine, but when installing SP2 or upgrading to SP3 using AutoYaST, the > > how do you upgrade with autoyast? you leave the partitioning as it is but > format all system-relevant parts? If we stick to the installation of SP2 for now, then I format md* and initialize both physical drives (added the initialize manually). Changing persistent_superblock from false to true has not changed the situation. What I find really strange about the upgrade profile (generated as the last step during the upgrade) also formats all partitions ??? So that one would probably never work anyway... I have attached an archive of the partition tag of both SP2 installation and SP2-->SP3 profiles. > >> /boot/grub/menu.lst refers to /dev/md? and I have tried configuring >> device.map to map to both /dev/sd? and /dev/disk/by-id/*. Another funny >> observation : Switching the bootable flag from sdb1 to sda1 changes the >> boot error from "Invalid partition able" to "No operating system" >> >> So it looks like the RAID setup somehow does not make it to disk when using >> AutoYaST. >> >> Any ideas ? > > the only idea and bug that comes close to it is > https://bugzilla.novell.com/show_bug.cgi?id=581523 > it's about LVM but RAID was affected too. > SP3 accidently pulls in multipath drivers into the ramdisk and those make > trouble during the reboot. > But actually your sympthons are a bit different, so I have doubts that you > hit > that problem. Thank you for any inspiration. //Andreas

2 2