October 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] autoyast from command line/shell ?
by abhijit 09 Oct '07

09 Oct '07

hi, i am trying to build a multi-distro installer (loaded via pxe) and want to invoke autoyast from command line/shell passing the autoinst.xml file to drive the install. i have the following questions: 0. is this possible? because i've always seen autoyast being invoked via "linuxrc". looking up linuxrc source it seems quite a fair bit of setup needs to be done before invoking autoyast. i dont (and cannot use) "linuxrc" as my "init" program. 1. if its possible, is there a doc or link that describes the environment (files/directory structure/shell-vars etc.) that needs to be setup before invoking autoyast? 2. what should the command line look for the invocation: something like: # yast ??? if all this is already mentioned in some document, i'd be more than glad to go thru it. link please? thanks a lot in advance s. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 7

[opensuse-autoinstall] updates in 10.3
by Simon Crute 09 Oct '07

09 Oct '07

Hi Uwe/List, Looking through the changes with 10.3 document at http://www.suse.de/~ug/autoyast_changes_10_2-10_3.html there's some features I'd love to use in my SLE script files (the improvements to the ask scripts for a start) Is it possable to package the ask.ycp into a driver update file ? Thanks. -- Simon Crute IS&T. Bracknell. UK. -- 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] Bug in RootPart.ycp (?)
by Mike Marion 09 Oct '07

09 Oct '07

(?) because I'm not sure if this is a design decision based on it not being possible to work, if it can't know the directive to reformat /. Anyway... I ran into a situation where re-installing the same OS image (SLED10-SP1 in this case) while re-using the existing fstab and partitions, from 32bit to 64bit, or vice versa, fails on the partition check. I narrowed this down to the RootPart script and check for which partition is the root one. I understand why this fails in most cases, however, it still fails when using a profile that says to reformat /. As a work around, I figured out how to create an override RootPart.ycb and created a driverupdate which works. However it just assumes it's ok whether the root partition is formatted or not (I copied the code bit that says it's ok to install to/from ppc/ppc64 and put in i386 and x86_64). -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Statler -- Well, how do you like the film? Waldorf -- I've seen detergents that leave a better film than this. -- From _The Muppet Movie_ (1979) [Note: those are the grumpy old guys] -- 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] Autoyast of openSUSE 10.3 from an openSUSE 10.2 system: CD1/boot/x86_64/root is an unrecognized filesystem type
by Dan Stromberg 08 Oct '07

08 Oct '07

When I try to autoyast a system with openSUSE 10.3 from an openSUSE 10.2 install server, using an old kernel that was for openSUSE 10.2, it's not automatic. Instead, I get a menu system, and the menu system doesn't install - it just says "Loading installation system" and then goes right back to the earlier menu. If I alt-F3, I see: Loading image "ftp10-2/openSUSE-10.3-community-edition/CD1//boot/x86_64/root"... /download/image0: unknown fs type mount: /download/image0: No such file or directory So looking at the 10.2 install server, and comparing the CD1/boot/x86_64/root files for 10.2 and 10.3, I see the following difference: # file ~ftp/ftp10-2/ftp10-2/CD1/boot/x86_64/root /srv/ftp/ftp10-2/ftp10-2/CD1/boot/x86_64/root: Linux Compressed ROM File System data, little endian size 74162176 version #2 sorted_dirs CRC 0xaeeee8a4, edition 0, 44848 blocks, 7088 files suse-boot-install-root:/srv/ftp/ftp10-2/openSUSE-10.3-community-edition/CD1/boot/x86_64 x86_64-suse-linux 30908 - above cmd done 2007 Fri Oct 05 05:12 PM # file ~ftp/ftp10-2/openSUSE-10.3-community-edition/CD1/boot/x86_64/root /srv/ftp/ftp10-2/openSUSE-10.3-community-edition/CD1/boot/x86_64/root: Squashfs filesystem, little endian, version 3.0, 0 bytes, 7942 inodes, blocksize: 65536 bytes, created: Wed Sep 26 13:20:07 2007 suse-boot-install-root:/srv/ftp/ftp10-2/openSUSE-10.3-community-edition/CD1/boot/x86_64 x86_64-suse-linux 30908 - above cmd done 2007 Fri Oct 05 05:13 PM It appears that the "root" filesystem format has changed in 10.3, and the install environment of 10.2 doesn't support that new fiklesystem format. If I set up a system with squashfs, can I just convert root to ext2 or somethiung to get this 10.2 install server and kernel to install 10.3 systems - and if that works, will there likely be other issues waiting to be discovered? Or do we need to upgrade our install server? Or could I just upgrade the kernel that's used for the install to something from 10.3, including a squashfs? I tried building my own kernel with squashfs in it, but that's giving me "invalid module format" on some insmod's. Thanks! -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 1

[opensuse-autoinstall] Problem with autoyast and openSuSE10.3
by Rainer Krienke 08 Oct '07

08 Oct '07

Hello, I haveen using autoyast quite a while with 10.1 as well as 10.2. Now I tried to use the same autoinstall.xml file I successfully used for 10.2 for 10.3. However this fails in very early state. I install the maschine using SLP (just as I did for 10.2) by which it gets its network installation repository. The SLP parameters are like this: service:install.suse:http://installsrv.uni-koblenz.de/linux/suse10.3 autoyast=http://installsrv.uni-koblenz.de/linux/suse10.3/autoinstall.xml When I leave the autoyast part from this commandline everything works and after a while I see the yast interface. If I start the machine using the autoyast parameter from above, the system, starts loading the installation system but halts and says Loading Installation system (1kB) 100% No typo here. It really says the system is loaded 100% and is 1 kB in size. The installation system the says that it could not find the openSUSE Repository which works fine if I do not specify the autoyast-Parameter when booting. On console I can see a possible error butI do not know what it really means. Because this log is only written to the screen this exerpt here has been copied manually (it might contain a typo :-)) ): slp: using http://installsrv.uni-koblenz.de/linux/suse10.3 autoyast=http://installsrv.uni-koblenz.de/linux/suse10.3/autoinstall.xml ... loading http://installsrv.uni-koblenz.de/linux/suse10.3 autoyast=http://installsrv.uni-koblenz.de/linux/suse10.3/autoinstall.xml/content -> /content sha1 .... sha1 not checked loading http://installsrv.uni-koblenz.de/linux/suse10.3 autoyast=http://installsrv.uni-koblenz.de/linux/suse10.3/autoinstall.xml/content.asc -> /content.asc sha1 .... sha1 not checked signature ok loading http://installsrv.uni-koblenz.de/linux/suse10.3 autoyast=http://installsrv.uni-koblenz.de/linux/suse10.3/autoinstall.xml/boot/i386/root -> /download/file_000 sha1 .... sha1 check failed /download/file_000: unknown fs type instsys mount failed: boot/i386/root disk: mount ok but test failed .... What I identify as an error is in the last lines beginning with the failed sha1 check. I tried to loop mount this root-image manually on a 10.2 system and this does not work since it is a squash fs. The correspondig root image from 10.2 is a regular image. When I try to mount the 10.3 root image I get: bliss:/import/sw/linux/suse10.3/boot/i386 # mount -o loop root /mnt mount: you must specify the filesystem type bliss:/import/sw/linux/suse10.3/boot/i386 # file root root: Squashfs filesystem, little endian, version 3.0, 0 bytes, 7943 inodes, blocksize: 65536 bytes, created: Wed Sep 26 22:22:45 2007 So I guess this is the error. But how can I work around this problem? Why does it work if i do not specify the autoyast parameter at all? Do I have to change my autoinstall.xml file and if how? Thanks for any help Rainer -- Rainer Krienke, Uni Koblenz, Rechenzentrum, A22, Universitaetsstrasse 1 56070 Koblenz, Web: http://www.uni-koblenz.de/~krienke, Tel: +49261287 1312 PGP: http://www.uni-koblenz.de/~krienke/mypgp.html, Fax: +49261287 1001312

1 0

[opensuse-autoinstall] Synchronizing a set of installed packages with another system
by Paco Cruz 07 Oct '07

07 Oct '07

Hi all I am trying to upgrade a bunch of OpenSUSE 10.2 PCs to 10.3 using autoyast. The normal upgrade has failed in my test machine (lots of missing dependencies that, when ignored or resolved, resulted in a broken installation) so I need to make a fresh 10.3 install and synchronize it (add missing packages and delete unwanted ones) with a list of packages installed in my 10.2 installation. I can "rpm -qa >> rpms.txt" in my test machine and clean it to suit my needs, but I don't know how to apply that list to an already installed system. What I am looking for is info/help on how to get the list of packages (in fact applications and their dependencies) installed in my test system, and how to replicate them to a fresh OpenSUSE 10.3 installation. Thank you all -- Saludos Paco Cruz --------------------------------------------------------------------- If you think that training is expensive and complicated, try ignorance instead. Roy Crock (founder of McDonalds) Si crees que el aprendizaje es caro y complicado, prueba con la ignorancia. --------------------------------------------------------------------- -- 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] sles 9 http install over ports other than 80
by John Willis 06 Oct '07

06 Oct '07

the source code for linuxrc indicates the install= option ignores http URL ports unless a special format is used to download stage2 over http but the real problem seems to be when linuxrc writes the key values to install.inf for yast2 it doesn't append the http URL port to ServerIP does anyone know if this was by design, or could it be a bug? Thanks -- 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] AutoYaST and OpenSUSE 10.3
by Lee Mayes 05 Oct '07

05 Oct '07

Hello all, I'm attempting to use AutoYaST on the new OpenSUSE 10.3 bits released yesterday. I've tried both i386 and x86_64. While I guess this is more of a syslinux problem than AutoYaST, someone here might be able to shine some light on the problem I'm seeing. When creating AutoYaST install ISO's, my code puts autoyast.xml and info in the root of initrd. Previous to 10.2, syslinux would automatically find info there, however starting with 10.2 you must specify it implicitly in boot params. That change is outlined here: http://www.suse.de/~ug/autoyast_doc/appendix.linuxrc.html What I'm using in isolinux.cfg is: append initrd=initrd ramdisk_size=65536 splash=silent showopts text netwait=5 autoyast=file:///autoyast.xml info=file:///info On my 10.3 installs, they abort immediately saying "Couldn't find the OpenSUSE repository". Looking at what's logged on virtual console #3 after the install halts, I see: <modules loading> info file: file:///info loading file:/info -> /info error 37: Couldn't open file /info repository: looking for cd:/ <rest snipped, it's a ~16MB minimal ISO created from boot/$ARCH/loader, so no OS depots to be found> Here's what's in /info at the top level of initrd.img: Serverdir: /LinuxCOE/OpenSUSE/10.3/i386/ InstMode: http Server: 192.168.1.1 Textmode: 1 Netdevice: eth0 A manual install pointing at this network source succeeds, and I've tried several different formats for file:/info. I didn't see anything mentioned in the 10.2 -> 10.3 delta document, anyone have an idea what else I can try? The exact say isolinux.cfg and file placement works great on <=10.2 and SLED/SLES. Best Regards, Lee -- 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] advanced rules.xml configuration
by Johan Hansson 05 Oct '07

05 Oct '07

Hi have a problem with my rules.xml file and using the predefined attributes product and product_vendor to match different hardware profiles. The problem occurs on SLES10-SP1-x86_64 and on HP ProLiant hardware. Tested on both HP ProLiant DL380 G3 and ProLiant BL465c G1. Autoyast doesn't seem to be able to figure out neither the product or the product_vendor and delivers an empty string. This is what comes out of the y2log i2007-10-05 16:56:24 <1> 172.31.1.117(3358) [YCP] AutoInstallRules.ycp:397 file: classes/@product_vendor@.xml 2007-10-05 16:56:24 <1> 172.31.1.117(3358) [YCP] AutoInstallRules.ycp:410 var: product_vendor 2007-10-05 16:56:24 <1> 172.31.1.117(3358) [YCP] AutoInstallRules.ycp:576 Final Profile name: classes/.xml 2007-10-05 16:56:24 <1> 172.31.1.117(3358) [YCP] AutoInstallRules.ycp:390 Bash return: if ( [ "1" = "1" ] ) ; then exit 0; else exit 1; fi ($["exit":0, "stderr":"", "stdout":""]) ($["custom1":"default", "mac":"000f20f9e8c9", "product_vendor":""]) Parts of the rules.xml file <rule> <product_vendor> <match>*</match> </product_vendor> <result> <profile>classes/@product_vendor@.xml</profile> <continue config:type="boolean">true</continue> </result> </rule>  <rule> <mac> <match>*</match> </mac> <result> <profile>srvconf/autoyast-@mac@.xml</profile> <continue config:type="boolean">false</continue> </result> </rule> The syntax of all xml files is checked. and all other rules has no problems. Have been matching the products with the information from dmidecode. Same thing happens for ex on the rule below <rule> <product> <match>ProLiant BL465 C1</match> <match_type>exact</match_type> </product> <result> <profile>classes/HPBL465c.xml</profile> <continue config:type="boolean">true</continue> </result> </rule> Anyone has any ideas what could be wrong? Regards Johan -- 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] YaST got signal 1 at YCP file :174
by Alan Mosca [CRI] 04 Oct '07

04 Oct '07

Hi all, I'm seeing a very strange behaviour after moving from SLES10 to SLES10 SP1 on some systems. We are using the same autoyast.xml as we were before, and on i386 it seems as it isn't running the embedded scripts. On x86_64, when it gets to the second stage of the install (after the reboot) the install stops and returns the message in the subject. I have attached autoyast.xml so you can take a look if it might be something wrong there, but I also noticed that in another office they are using SP1 and the same file and everything works ok. Are there any specific logs I should be looking at? /var/log/YaST2/y2log doesn't seem to have any errors. I can provide the whole /var/log/YaST2 folder if needed. Thanks again guys! -- Alan Mosca

1 1