June 2010 - openSUSE Autoinstall - openSUSE Mailing Lists

AW: [suse-autoinstall] auto install with service pack
by Martin.Linten＠rzf.fin-nrw.de 15 May '25

15 May '25

Hallo Anas, hallo list! I am trying to install sles8 with service pack 2 in an automated way. The kernel and the inird from the sp2-CD (chosen because of hardware support) are booted via pxe. When checking the software selection I always get a long list of dependency errors beginning with "aaa_skel not available..." and so on. Please help and tell me how I can do better! I suppose it has nothing to do with the /UnitedLinux-i386-1 directory, but maybe I am wrong... My nfs-exported directory for linuxrc looks like this: |--boot | `--loader |--content (file from sles8) |--media.1 (from sles8) |--sles8 | |--UnitedLinux | |--boot | |--docu | |--dosutils | |--media.1 | |--media.2 | |--media.3 | |--suse | `--yast |--sp2 | |--UnitedLinux | |--boot | |--docu | |--i386 | |--images | |--linux | `--media.1 `--yast |--ul |--instorder (file) `--order (file) I011-52:/autoinst/suse/sles8sp2/yast # cat order /sles8 /sles8 /sp2 /sp2 I011-52:/autoinst/suse/sles8sp2/yast # cat instorder # I want to prefer sp2 packages if possible /sp2 /sp2 /sles8 /sles8 Thanks a lot, Martin -----Ursprüngliche Nachricht----- Von: Anas Nashif [mailto:nashif@suse.de] Gesendet am: Dienstag, 15. Juli 2003 09:39 An: Aaron McSorley Cc: suse-autoinstall(a)suse.com Betreff: Re: [suse-autoinstall] auto install with service pack Hi, It can be done in an automated way. For example, my nfs export for SLES8 i386 with SP2 looks like this: |-- SP2 | |-- UnitedLinux | |-- boot | |-- docu | |-- i386 | |-- images | |-- linux | `-- media.1 |-- SuSE-Linux-SLES-i386-8 | `-- CD1 | |-- boot | |-- docu | |-- media.1 | |-- suse | `-- yast |-- UnitedLinux-i386-1 | |-- CD1 | | |-- UnitedLinux | | |-- boot | | |-- docu | | |-- dosutils | | `-- media.1 | `-- CD2 | |-- UnitedLinux | |-- boot | `-- media.2 |-- boot | `-- loader |-- media.1 `-- yast `-- ul in the directory yast, there are 2 files: order and instorder This is the content which references the location of the root of every source. (where the media.1 directory is available) # cat yast/instorder /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 avicenna:/work/CDs/sles8-i386 # cat yast/order /SP2 /SP2 /SuSE-Linux-SLES-i386-8/CD1 /SuSE-Linux-SLES-i386-8/CD1 /UnitedLinux-i386-1/CD1 /UnitedLinux-i386-1/CD1 (delimiter is tab) more details can be found at http://www.suse.de/~nashif/autoinstall/8.1/html/advanced.html#AEN1251 Hope that helps... Anas Aaron McSorley wrote: > Is there a method for incorporating a service pack into an > auto install of SLES8. > > I tried putting the service pack in its own directory in my auto install > repository > and giving it preference in the order and instorder directories. > The install starts ok but, after package install I get alot of package > install failures. > After hitting ok to the fail log it prompts me to insert the service > pack cdrom. > > I thought about just replacing the original packages with the new ones > from the service pack but, > I would like to keep the service pack separate from the original > repository so I can > install without it if I want. > > thanks > -- To unsubscribe, e-mail: suse-autoinstall-unsubscribe(a)suse.com For additional commands, e-mail: suse-autoinstall-help(a)suse.com

3 2

linuxrc - netdevice=<hwaddress>
by John Willis 18 Dec '12

18 Dec '12

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

3 2

[opensuse-autoinstall] Repository Priority
by Tim Kirby 28 Sep '11

28 Sep '11

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- 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] OT: Centralized patch management for OpenSuse 11.x
by Ivan De Masi 14 Jan '11

14 Jan '11

Hello, someone may start to laugh now for my (OT) question, but I can't find a satisfying solution :-/ How do you manage patches, updates, etc. for your running opensuse clients (not enterprise linux, just the "regular" opensuse distribution)? Is there a way like known from M$-World (WSUS)? As I know "Zend Management Server" is not open source (and not supported any more?!). Or can the complete management only be handled with self written scripts? 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 3

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

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

[opensuse-autoinstall] general rules question
by dutchguy69 26 Jul '10

26 Jul '10

I have a working autoyast install for 11.1 without using rules. Right now I would like to introduce rules but I do not seem to understand exactly how to make this work. The current install is done by supplying information for a linuxrc info file on the kernel command line info=nfs://<ip-address>/<path>/1055_init.linuxrc The info file has several parameters defined for network access, the install and the autoyast variable autoyast: nfs://<ip-address>/<path>/1055_init.autoyast <- this is my autoinst profile below the path I have created the rules directory which includes a rules .xml file with following content <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/rules.dtd">  <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <rules config:type="list"> <rule> <custom1> <script> # CPU_TYPE on vm's is giving same result for CPU as on real hardware we have to extend to video to understand the difference between virtual and real CPU_TYPE=`cat /proc/cpuinfo|grep 'model name'|uniq|awk 'BEGIN {FS=":"};{print $2}'` VIDEO_TYPE=`/sbin/lspci | grep "VGA compatible controller"|awk 'BEGIN {FS=":"};{print $3}'` if [ "$CPU_TYPE" == " AMD Athlon(tm) 64 X2 Dual Core Processor 4400+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host1.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host1-virtualbox.xml" fi # information for scan64-3200 elif [ "$CPU_TYPE" == " AMD Athlon(tm) 64 Processor 3200+" ]; then if [ "$VIDEO_TYPE" == " nVidia Corporation G70 [GeForce 7300 GT] (rev a1)" ]; then echo -n "host2.xml" elif [ "$VIDEO_TYPE" == " InnoTek Systemberatung GmbH VirtualBox Graphics Adapter" ]; then echo -n "host2-virtualbox.xml" fi fi </script> <match>*</match> <match_type>exact</match_type> </custom1> <result> <profile>@custom1@</profile> <continue config:type="boolean">true</continue> </result> </rule> <rule> <custom> <script> </script> <match>*</match> <match_type>exact</match_type> </custom> <result> <profile>1055_init.autoyast</profile> <continue config:type="boolean">false</continue> </result> </rule> </rules> </autoinstall> I have tried to change the autoyast parameter in the info file with the following values autoyast: nfs://<ip-address>/<path>/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/ <-- question about profile location autoyast: nfs://<ip-address>/<path>/rules/rules.xml Above direct reference to rules file seems to work but not as expected. When I check the box I can see that in /tmp/profile/autoinst.xml I find a copy of my rules.xml file where I'm expecting a merged profile from my 1055_init.autoyast and host2.xml information I'm not sure exactly what I'm doing wrong and even after extensive check via google haven't found the right references. I've used http://forgeftp.novell.com/yast/doc/SL11.1/autoinstall/ for documentation but it is not giving me enough detail to solve above issue. Any input would be welcomed. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 5

[opensuse-autoinstall] Problem with disk device names
by Peter Pointner 15 Jul '10

15 Jul '10

Hello, I am trying (on openSuse 11.2) to create a rules file and classes to create a software raid if the pc has 2 hard disks. My first try is to use disksize rules for /dev/sda and /dev/sdb. This failed, because I booted from USB stick, and the first SATA disk became /dev/sda, the USB stick became /dev/sdb, and the second SATA disk became /dev/sdc. Probably I will find a way to find out if there are 2 disks, but what to use for the "device" attribute of the "partitioning" section? Is there a generic way to specify the first, second, ... harddisk without getting disturbed by USB sticks? Peter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

5 12

[opensuse-autoinstall] ssh based installation for phase 1 only?
by Jochen Schaefer 29 Jun '10

29 Jun '10

Hi list, is there any way to perform an autoyast installation via ssh for phase 1 only and let the second stage run automatically without ssh? Thanks, Jochen Mit freundlichen Grüßen Novell GmbH, Jochen Schaefer Senior Consultant - Novell Services - Mobile: +49 (0)173 5876 969 Fax.: +49 (0)211 - 5631 3769 e-mail: jschaef(a)novell.com Location: Düsseldorf, Deutschland Novell GmbH, Düsseldorf; GF: Dr. Jürgen Müller, Sylvia Geil, Felix Imendörffer; HRB 21108 (AG Düsseldorf) Ready for enterprise-class consulting www.novell.de/consulting -- 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] sles11 sp1 problem on add_on section in xml file
by Ruediger Gunreben 29 Jun '10

29 Jun '10

Hello, I've a Problem with the SP1 on SLES11. I have the following xml file sniplet which will be merged by the rules.xml file during autoyast installation Condition: ================================================ <?xml version="1.0"?> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"> <listentry> <media_url>cd:///?devices=/dev/sr0,/dev/sr1</media_url> <product>IsarFlowAddons</product> <product_dir>/addons/isarflow</product_dir> <ask_on_error config:type="boolean">true</ask_on_error> <name>IsarFlowAddons</name> </listentry> ... ================================================ When I've a look at the processed /tmp/profile/autoinst.xml file after the merging during the installation process the media_url entry looks like this: Problem: ================================================ <media_url><![CDATA[cd:///?devices=/dev/sr0,/dev/sr1]]></media_url> ================================================ Thus the add_on_products won't be found and the Directory and Repository Name will be declared as 'Unknown' in the installation section of add_products. Can anyone help me with this problem? Workaround(?): I'll try to make a "sed" pre-script substitution. I'll let you know it it works. 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 3

[opensuse-autoinstall] Unable to Create Repository SLED 11.0
by Bart Wahlgren 28 Jun '10

28 Jun '10

I used Yast Product Creator to create a custom installation DVD for SLED 11.0. AutoYast fails when trying to create the repository with the following error: Unable to create repository from 'url dvd:///' Details Valid metadata not found at specified URL History - Signature verification failed for content Does anyone have suggestions on what I did wrong in the configuration of the product or how to troubleshoot this error? Thanks Bart Wahlgren Network Administrator Speed Script Pharmacy Systems Direct: 913-643-2454 Fax: 913-894-1802 bwahlgren(a)speedscript.com 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] "Invalid partition table" on SLES10SP2/3 with soft RAID
by Andreas Taschner 17 Jun '10

17 Jun '10

Hi This may very well not be an AutoYaST problem, but ... 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 system fails to boot and reports "Invalid partition table" before even reaching the grub menu. Whether I use initialize true on sda, sdb and md in the installation profile or not, makes no difference. The strange thing is when I install SLES manually after being in the error situation, it recognizes all partitions and RAID setup. When booting into rescue mode and doing an fdisk -l it sees all sd{a,b}* partitions correct, bootable is /dev/sdb1. It also lists the /dev/md{0-4], but only md0 is claimed to contain a valid partition table (though not containing any partitions). md1-4 are marked as invalid. mdadm --scan --detail print shows that all RAID devices contain two devices. /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 ? Thank you. Best regards Andreas Taschner Designated Support Engineer Novell -- 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] registration against SMT using autoyast
by Matthew Delves 08 Jun '10

08 Jun '10

Hey List, I'm wondering if there is a known way of registering a server against SMT using autoyast. Thanks, Matt Delves. -- --------------------------------------------- Matthew Delves System Administrator Information Systems Networks & Infrastructure University of Ballarat ph: 03 5327 9732 email: m.delves(a)ballarat.edu.au -- 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] What should my module return?
by Erico Mendonça 02 Jun '10

02 Jun '10

I'm running a self-written YaST module at the start of the installation (via control.xml, inserted right before the prepareprogress module), and even though my modules finishes with success, I get a YaST error (red screen). Do I need to return/set any specific values? I already tried returning true/false/0/1/nil/GetInstArgs(0), etc, all with the same result. There doesn't seem to be any specific error messages in the log, it just informs that the YaST client module was finished. -- -- Erico -- 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] grub boots wrong kernel after stage 1
by Antje Bendrich 01 Jun '10

01 Jun '10

Good morning, we are using PXE to boot into autoyast and install the packages from local repositories via http and are having a problem since Suse released a new kernel package in April. Everything works fine up to the first reboot after finishing stage 1. Then grub has two kernels to choose from: 2.6.31.12-0.1-default, which is the kernel of the autoyast installation, and 2.6.31.12-0.2-desktop, which is the newest kernel freshly installed from our repositories. Grub boots the 2.6.31.12-0.1-default-kernel, complains (with good cause) 'unable to canonicalize path "/lib/modules/2.6.31.12-0.1-default/systemtap/preloadtrace.ko": No such file or directory' and continues booting, but fails to load the modules for the network card and the graphics card (and probably others). This leads to X not starting and -worse- autoyast failing to load some configuration files via ftp, configured like this: <file> <file_path>/etc/somefile</file_path> <file_owner>root:root</file_owner> <file_permissions>644</file_permissions> <file_location>ftp://somehost/files/etc/somefile</file_location> </file> Autoyast does not complain very visibly about this failure while it's running. The files not loaded do exist on the system afterwards, alas with a size of 0 bytes. The normal system logs do not contain that first boot, so it is kinda hard to figure out exactly why the final system does not work like it should. If I babysit the installation and manually choose the other kernel version (2.6.31.12-0.2-desktop) when grub comes up after stage 1, everything continues like it should, but I don't really want to wait to hit "down down return" at the exact right time... So: Why is the installation kernel still configured in grub when it is not fully functional anymore? How do I get rid of it at this early time? Or is our error something else entirely? Thanks in advance, Antje -- Antje Bendrich (Team IT-Services), Phone +49 40 808077-642 DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone +49 40 808077-555 Sitz / Register: Hamburg, AG Hamburg, HRB 88805, Ust-IdNr.: DE 232129737 Sachsenstraße 5, 20097 Hamburg/Germany, CEO: Dr. Klaus-Peter Kossakowski

2 5

[opensuse-autoinstall] Cannot create raid with autoyast on 11.3 M7
by Peter Pointner 01 Jun '10

01 Jun '10

Hello, I try to create a raid-1 with autoyast on opensuse-11.3 Milestone 7 x86_64. It fails with "Error while configuring partitions. Try again." The same xml-file works with opensuse-11.2 x86_64. Did I miss relevant changes between 11.2 and 11.3? Should I provide more information here on the list or open a bug on bugzilla? Peter -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3