- openSUSE Autoinstall

[opensuse-autoinstall] "SHA1 sum wrong" after modifying control.xom
by Andreas Taschner 06 Oct '09

06 Oct '09

Hi I have created a YaST client module that snaps into the AutoYaST workflow for running displaying the progress of custom scripts (http://www.novell.com/communities/node/8961/) and a part of this game is to modify <instsrc>/control.xml. While this works fine for SLES 10, SLES 11 is more careful. First it gave me an error like this : <instsrc>/control.xml : SHA1 sum wrong. If you really trust your repository, you may continue in an insecure mode. (OK/Back) Hmm ... OK fair enough - naively I entered a new SHA1 sum in <instsrc>/content hoping that would be it. :( Now I get a less friendly popup saying : <instsrc>/content: Invalid signature Aborting installation I see there is a content.key file, but since I don't know the password to it, it guess it is useless to try to generate a new content.asc. Is there any way around this, or do we not want customer's to port their customizations to SLE 11 ? Thanks. Best regards Andreas Taschner -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

4 4

[opensuse-autoinstall] Classes do not work in 11.1 autoyast installation
by mwani＠fkf.mpg.de 06 Oct '09

06 Oct '09

Hi, I want to use classes in my autoyast installation. With the 'autoyast' parameter I'm loading the xml-file: <?xml version="1.0"?> <!DOCTYPE profile> <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <classes config:type="list"> <class> <class_name>default</class_name> <configuration>software.xml</configuration> </class> <class> <class_name>laptop</class_name> <configuration>partitions.xml</configuration> </class> </classes> </profile> I'm booting the client via PXE boot. I can see in the log file of the http server, that the client fetches the xml file. But in contrast the client does not even try to load the class files. I can not see an obvious error in the y2log file. With 10.3 that procedure worked that way. With 11.1 it has broken for me. Any hints are appreciated. thanks, Michael Wanitschek -- 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] Autoinstallation of SLES 10.2 is failing with addition of custom add-on, possibly due to placement of gpg key for custom add-on
by Jason Babicka 03 Oct '09

03 Oct '09

This is my first email to this list, so I will try to include as much information as possible to describe my problem. I am trying to make a custom DVD that includes all of the standard SLES 10.2 files along with an RPM for my companies product. I think that the problem that I am running into is due to not placing the gpg for my companies product in the correct location, but I am not entirely sure at this point. Let me describe what I have done so far and hopefully someone can help me see where I may have gone wrong. Here is what I did to set up the directory for building the iso: 1. I copied the contents of the entire SUSE 10 SP2 DVD into /[path_to_dvd_contents]/isoroot/ 2. I think followed this link < http://www.suse.de/~ug/AutoYaST_FAQ.html#b9> that Uwe Gansert wrote about adding your own RPMs to an SLES installation source a. I used version 20060925 of the create_update_source.sh script b. I copied our owned signed RPM to /[path_to_dvd_contents]/updates/suse/i586/ c. I then ran the following commands from /[path_to_dvd_contents]/isoroot/updates/suse/ (as outlined in create_update_source.sh description from here <http://en.opensuse.org/Inst-source-utils#Short_description_of_the_scripts>) i. create_package_descr -x setup/descr/EXTRA_PROV ii. cd setup/descry iii. create_directory.yast . iv. create_md5sums . d. Opting now to add this installation source to our existing autoinst.xml files, I created an add_on_products file located at /[path_to_dvd_contents]/isoroot/add_on_products i. The contents of this file is just "dvd:///updates" 3. I then followed this link <http://www.suse.de/~ug/AutoYaST_FAQ.html#bB> that Uwe Gansert wrote for signing an add-on product with our gpg key 4. At this point I would run the mkisofs command to build the iso I tested this by installing this custom installation DVD on a VM. Using an existing autoinst.xml file, I began installing on the VM. When it gets to the portion where it tries to configure the software selections, a window is displayed that says: +--------------------------------------------+ | Error occurred while creating the catalog. | | | | +-----------------------------+ | | | dvd:///updates | | | | Source rejected by the user | | | +-----------------------------+ | +--------------------------------------------+ I noticed that when this message was displayed, that it was trying to download from dvd:///updates/content.key which lead me to think that I needed to re-sign our add-on product properly. I followed this link <http://www.suse.de/~ug/AutoYaST_FAQ.html#bB> that Uwe Gansert wrote for signing an add-on product with our gpg key. After completing these steps, I redid step 2c that I listed above and remade the iso. I again tested this by installing this custom installation DVD on a VM. Using the same existing autoinst.xml file, I began installing on the VM. When it gets to the portion where it tries to configure the software selections this time, the following error message is displayed: +----------------------------------------------------------------------------------------------+ | Error | | | | The package resolver run failed. Please check your software section in the autoyast profile. | +----------------------------------------------------------------------------------------------+ Looking at the software section of the autoinst.xml file that I am using looks like this: <software> <patterns config:type="list"> <pattern>base</pattern> <pattern>ha_sles</pattern> </patterns> <packages config:type="list"> <package>emacs</package> <package>[custom_rpm_name]</package> <package>ipsec-tools</package> <package>perl-Net-Daemon</package> <package>perl-XML-RegExp</package> <package>perl-PlRPC</package> <package>perl-Data-ShowTable</package> <package>perl-XML-DOM</package> <package>perl-DBD-mysql</package> <package>perl-DBI</package> </packages> </software> If anyone can provide any suggestions for other things to try or perhaps where I may have gone wrong, I would greatly appreciate it. If you need more information then please let me know. Thank you, Jason Babicka -- 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] Wrong disk-id with hw raid
by Tomas Rosenthal 24 Sep '09

24 Sep '09

Hi I'm having a problem with hardware raid and autoyast. First some background, I have the following setup: * HP ProLiant DL380 * SLES11 autoinstaller - all in one DVD * HP HW raid controller to set up hardware raid 5 on the system. * The software to set up hardware raid is put into the initrd of the SLES DVD A precondition is to be able to install without network and to bundle everything in one install DVD. The autoyast installer launches a pre-install script that sets up the hardware Raid. Now the actual problem: The data in /dev/disk/by-id is read and memorized by yast before raid is set up. After the raid setup script has completed all values have changed in /dev/disk/by-id. This causes the installer to crash when it later tries to set up Grub. Yast inserts the incorrect values it remembers into /boot/grub/device.map. The installer crashes with this error in y2log_bootloader: grub> setup --stage2=/boot/grub/stage2 --force-lba (hd0) (hd0,0) Error 21: Selected disk does not exist grub> quit Is it possible to make the yast bootloader re-read the values from /dev/disk/by-id before setting up grub? I tried to simply override the values in the files it touches in a chroot script, but yast simply removes my changes and creates a new incorrect file in its place. I have also tried to add the raid script to /etc/init.d/ inside initrd of the SLES installer, but I can't link it like I would on debian. Googling this I found that I need to run 'insserv' but I can't chroot into the initrd in any way to do this. I'm not even sure running it in a runlevel really early would be enough, but this is an option I have not been able to test fully, so some pointers or a link on where I can find info on setting up init-scripts in suse without insserv would be greatly appreciated. Warm regards, Tomas Ps. Thanks Uwe for solving the issue '[opensuse-autoinstall] Rule based auto-installation without network' for me Ds. -- 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] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- 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] openSUSE11.2-Milestone6 / rules / xsltproc missing!?
by Guenther Haas 09 Sep '09

09 Sep '09

Hi all! Today I spent some time testing our 11.1 autoinstallation with pxe boot, autoyast and rules with openSUSE-11.2-Milestone6 (from the DVD, 32 and 64 bit). After some minor problems and changes (mounting of our own scripts doesn't work because of missing portmap and nonworking(?) rpc.statd except I use the mount option "nolock"), the installations stops with the following error message and problem in the step "Processing Profiles and Rules": "sh: /usr/bin/xsltproc: No such file or directory" Clicking "OK" several times the next message says "A profile for this machine counld not be found or retrieved Check that you entered the correct location...". And in the logfile 'y2log" I find the following information > ... > > 2009-09-09 12:43:05 <1> sirius(3901) [YCP] AutoInstallRules.ycp:679 > Working on file: classes/netcard/primergy_rx300.xml > 2009-09-09 12:43:05 <1> sirius(3901) [YCP] AutoInstallRules.ycp:711 > Merge command: /usr/bin/xsltproc --novalid --param replace "'false'" > --param with > "'/tmp/YaST2-03901-2AVCCM/rules/classes/netcard/primergy_rx300.xml'" > --output /tmp/YaST2-03901-2AVCCM/result.xml > /usr/share/autoinstall/xslt/merge.xslt > /tmp/YaST2-03901-2AVCCM/base_profile.xml > 2009-09-09 12:43:05 <3> sirius(3901) [bash] > ShellCommand.cc(shellcommand):78 sh: /usr/bin/xsltproc: No such file > or directory > 2009-09-09 12:43:05 <1> sirius(3901) [YCP] AutoInstallRules.ycp:713 > Merge result: $["exit":127, "stderr":"sh: /usr/bin/xsltproc: No such > file or directory\n", "stdout":""] > 2009-09-09 12:43:05 <3> sirius(3901) [YCP] AutoInstallRules.ycp:716 > Merge Failed > 2009-09-09 12:43:05 <1> sirius(3901) [ui] > YPushButton.cc(setFunctionKey):183 Guessing button role YOKButton for > YPushButton "OK" at 0x8c8d6dc from function key F10 > 2009-09-09 12:43:05 <1> sirius(3901) [ui-shortcuts] > YShortcutManager.cc(checkShortcuts):127 No valid shortcut for YLogView > "Error" at 0x8af621c And really, "/usr/bin/xsltproc" is not available at this point of the installation. No package "libxslt-....rpm" is installed (in the initrd?). So the merging of xml files, e.g. described in the following way > ... > > That requires that yast has started at least once and autoyast has > fetched the XML profile. > If you don't have problems with the rules scripts, but with the > merging, you can merge the XML files like AutoYaST would do it to view > the result: > /usr/bin/xsltproc --novalid --param replace "'false'" \ > --param dontmerge1 "'package'" \ > --param with "'a.xml'" --output out.xml \ > /usr/share/autoinstall/xslt/merge.xslt base.xml > > ... > in the article "Why to Confirm? (Part 2)" at http://ugansert.blogspot.com/2009/02/why-to-confirm-part-2.html doesn't work. Has anybody tested something similar and maybe can confirm that observation? Best regards, -- Guenther Haas, Uni Ulm, Institut TAIT, guenther.haas(a)gmx.de

1 0

[opensuse-autoinstall] Installation (SLES10-SP2) destroys USB Flash Drive
by Oliver Schweikert 08 Sep '09

08 Sep '09

Hello all, I read the autoyast profiles for installation from an USB flash drive. This worked so far with many different drives, but now i have a problem with a 8GB drive (Imation Nano Pro, with password protection). The first time, yast can successfully read the profile and starts the installation. The second time, after abort, the same drive cannot be accessed anymore. I made 2 test with 2 different computers: One drive has now invalid vendor, product name, etc, the second one seems to have valid metadata. But both fail to report anything by sfdisk or fdisk. I tried both types of URL: usb:///... and device://sdb1/... Has anyone an idea what yast (or another part of installation process) is doing, that could mess up the firmware? Maybe a USB/SCSI command, that is unusual to a USB drive? Best Regards, Oliver This are the kernel messages when plugging in a working drive: usb 4-2: new high speed USB device using ehci_hcd and address 6 usb 4-2: new device found, idVendor=0718, idProduct=043b usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: Nano Pro usb 4-2: Manufacturer: Imation usb 4-2: SerialNumber: 078C171929B4 usb 4-2: configuration #1 chosen from 1 choice scsi8 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 6 usb-storage: waiting for device to settle before scanning scsi 8:0:0:0: Direct-Access Imation Nano Pro PMAP PQ: 0 ANSI: 0 CCS sd 8:0:0:0: [sdb] 15646720 512-byte hardware sectors (8011 MB) sd 8:0:0:0: [sdb] Write Protect is off sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 sd 8:0:0:0: [sdb] Assuming drive cache: write through sd 8:0:0:0: [sdb] 15646720 512-byte hardware sectors (8011 MB) sd 8:0:0:0: [sdb] Write Protect is off sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 sd 8:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 8:0:0:0: [sdb] Attached SCSI removable disk sd 8:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete and this are the ones of the same drive after installation: usb 4-2: new high speed USB device using ehci_hcd and address 10 usb 4-2: new device found, idVendor=0718, idProduct=043b usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=3 usb 4-2: Product: Nano Pro usb 4-2: Manufacturer: Imation usb 4-2: SerialNumber: 078C171929B4 usb 4-2: configuration #1 chosen from 1 choice scsi12 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 10 usb-storage: waiting for device to settle before scanning scsi 12:0:0:0: Direct-Access Imation Nano Pro PMAP PQ: 0 ANSI: 0 CCS sd 12:0:0:0: [sdb] Attached SCSI removable disk sd 12:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete This is the output of the broken drive with the screwed up metadata. It is the same product as the other one! usb 4-2: new high speed USB device using ehci_hcd and address 11 usb 4-2: new device found, idVendor=13fe, idProduct=1d00 usb 4-2: new device strings: Mfr=1, Product=2, SerialNumber=0 usb 4-2: Product: USB DISK 30X usb 4-2: Manufacturer: usb 4-2: configuration #1 chosen from 1 choice scsi13 : SCSI emulation for USB Mass Storage devices usb-storage: device found at 11 usb-storage: waiting for device to settle before scanning scsi 13:0:0:0: Direct-Access USB DISK 30X 1.00 PQ: 0 ANSI: 0 CCS sd 13:0:0:0: [sdb] Attached SCSI removable disk sd 13:0:0:0: Attached scsi generic sg2 type 0 usb-storage: device scan complete -- Oliver Schweikert Software Development HORIBA Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen (Germany) Tel: +49 7158-933-413 Fax: +49 7158-933-613 Email: oliver.schweikert(a)horiba.com Geschäftsführer: Thomas E. Ehmann, Yuichi Muroga, Takashi Nagano Amtsgericht Stuttgart, HRB 213200 -- 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] Deriving hostname for .xml file from PXE client & setting values in /etc/sysctl.conf
by Simon Loewenthal/NL/Tele2 04 Sep '09

04 Sep '09

Dear all, Question 1: I am trying to construct a generic autoinst.xml file for several clients. The template I am using is the one generated from one server, an HP Blade, found in /root/autoinst.xml. I intend to use this from within a file called this, (the MAC address is made up) # cat /tftpboot/pxelinux.cfg/00-00-00-00-00-00-01 default SLES11 # install SLES11 - Dummy entry for generic profile label SLES11 kernel vmlinuz append initrd=initrd ramdisk_size=65536 install=nfs://10.205.8.145/export/sles11-dvd1-i586 hostip=10.205.8.123/24 autoyast=nfs://10.205.8.145/export/generica-sles11_i586-autoinst.xml netdevice=eth0 textmode=1 insmod=bnx2 The autogenerated file contains host specific entries like, <host> <hosts config:type="list"> <hosts_entry> <host_address>10.254.66.90</host_address> <names config:type="list"> <name>newHPserver newHPserver</name> </names> </hosts_entry> <hosts_entry> <host_address>127.0.0.1</host_address> <names config:type="list"> <name>localhost</name> </names> </hosts_entry> <hosts_entry> <host_address>127.0.0.2</host_address> <names config:type="list"> <name>newHPserver.it.lan newHPserver</name> </names> I would like to have this xml inherit the hostname, IP address from the client that called it. Question 2: In most cases these servers will run Oracle. Therefore I would like to some how add values for shmmni shmmax and so on for Oracle. I expect to have a separate .xml file somewhere that would set these values. What is the way to so this? I thought that I could use some xml like this but I don;'t know if this is the preferred way in the SUSE world? <script>echo "kernel.shmall = 2097152" >>/etc/sysctl.conf</script> How would I instruct autoyast to call this file? Regards, S. -- Simon Loewenthal/Tele2 GSM: +31 6 2000 5427 [ -d . ] || echo "Oh!" ******** IMPORTANT NOTICE ******** This e-mail (including any attachments) may contain information that is confidential or otherwise protected from disclosure and it is intended only for the addressees. If you are not the intended recipient, please note that any copying, distribution or other use of information contained in this e-mail (and its attachments) is not allowed. If you have received this e-mail in error, kindly notify us immediately by telephone or e-mail and delete the message (including any attachments) from your system. Please note that e-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be subject of unauthorized interception or other interference without the knowledge of sender or recipient. Tele2 only send and receive e-mails on the basis that Tele2 is not responsible for any such computer viruses, corruption or other interference or any consequences thereof. -- 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] createrepo breaks installation server
by Justin Kinney 03 Sep '09

03 Sep '09

Hello, I've got a sles 10 sp2 installation server accessed by clients via http which has been working fine. I recently used createrepo to build the repomd.xml and other files necessary to use this source as a repo for packages by zypper clients. This too seems to have worked for providing package dependencies for clients that were not originally installed on the host. My problem is that now, whenever I try to build a new host, I get a message similar to "cannot find pattern: base". The installation continues, but based on the package counts being installed, there are many missing packages. The system later fails while trying to install grub. Removing the repodata folder from the installation sources fixes this. How can I use the same repository to both offer installation sources and later be used as a zypper repo? Thanks, Justin -- 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] SLES10 SP2 how to integrate dud and autoyast?
by Thomas.Zimolong＠bmi.bund.de 03 Sep '09

03 Sep '09

Hello All! In short: I need to integrate an HP-delivered DUD in my network-based autoyast-configuration with loopback mounted installation sources. Here's the whole story (sorry for the lengthy description): I have an existing environment with a PXE-server and an autoyast install server. I have to install some HP blades (460c G6) with a FLEX10 emulated NIC that needs a newer version of kernel module bnx2x than provided by the SLES10SP2 initrd. Concerning the initrd, I replaced the initrd on the PXE-server with the one provided by HP according to : << http://h18006.www1.hp.com/products/servers/management/rdp/knowledgebase/000… 197.html>> The installation is started from pxelinux.cfg/default with the following lines: --snip label auto10sp2_x86_64 menu label SLES10 SP2 (64 Bit) Automatische Installation kernel sles10sp2_x86_64/linux append initrd=sles10sp2_x86_64/initrd ramdisk_size=131072 vga=791 splash=0 install=http://myserver.mydomain/inst_srv/SLES10_x86_64/SUSE-SLES-10-Service- Pack-Version-2/DVD1 textmode=1 lang=de_DE autoyast=http://myserver.mydomain/inst_srv/autoyast/sles10sp2_x86_64-default/ --snap So far everything works fine, the first stage of the autoyast installation runs without problems. Now I have to tell autoyast to use the HP-provided Driver Update Disk to install the module to the installed system. HP delivers a file that is to be renamed to "driverupdate" and to be placed in the installation source. The installation source consists of loopback mounts of the SLES10-DVDs. The Problem is, that autoyast seems to look for the file "driverupdate" which is the root of DVD1. Since this is an ISO9660 I can't place the file there. When I copy the whole DVD to the filesystem of the install server an put the driverupdate there, the installation works, but since disk space is an issue on my install server, this is not a long term solution. Now I was playing around with some ways to change the path to driverupdate. 1) I tried to hand over some command line options to the kernel, like "dud=http://myserver...." Or "driverupdate=http://myserver....", like described in << http://en.opensuse.org/Linuxrc#p_dud>> but none of them worked. Then I found << http://www.suse.de/~ug/autoyast_doc/info_file_format.html>> stating no "dud" or "driverupdate" parameter. Hm,...? 2) I tried to put the info file section in my autoyast profile like in 7.3.3 of << http://www.suse.de/~ug/autoyast_doc/invoking_autoinst.html#id339566>> but that also didn't work: --snip <init> <info_file><![CDATA[ # # Don't remove the following line: # start_linuxrc_conf install=http://myserver.mydomain/inst_srv/SLES10_x86_64/SUSE-SLES-10-Service- Pack-Version-2/DVD1 dud: http:// myserver.mydomain /inst_srv/SLES10_x86_64/SUSE-SLES-10-Service-Pack-Version-2/driverupdate # end_linuxrc_conf # Do not remove the above comment # ]]></info_file> </init> --snap As far as I understood, linuxrc looks for the info file but if this fails it looks for additional parameters on the kernel commandline. Could it be that "dud" or "driverupdate" isn't supported in SLES10SP2? Do I have to look for a bug in the HP initrd? I looked inside the initrd, but can't seem to find any file named "info". Any hints or experiences with that topic? Greetz Thomas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 4