November 2007 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Is it possible to install patterns in stage2?
by Razi Khaja 16 Nov '07

16 Nov '07

I have read that there is a <post-packages config:type="list"> element to enable installation of packages after the reboot during stage 2. Is there also a <post-patterns config:type="list"> tag to enable installation of patterns in stage 2? How difficult would it be to implement this? -- 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] Would like to create a single frametitle around 2 questions with <ask>
by Razi Khaja 16 Nov '07

16 Nov '07

Ive created a reference profile for my system using the Autoinstallation module in Yast2 and added the xml below in the <general> section. When running an installation using autoyast, a dialog appears showing 2 frametitles surrounding each question's textbox. How would one go about creating a single frametitle surrounding both questions? <ask-list config:type="list"> <ask> <stage>initial</stage> <title>My Server Customization</title> <dialog config:type="integer">1</dialog> <element config:type="integer">1</element> <frametitle>Hostname and Domain Name</frametitle> <help>1. Enter the hostname of the server. </help> <question>1. Hostname</question> <path>networking,dns,hostname</path> <default>test</default> </ask> <ask> <stage>initial</stage> <title>My Server Customization</title> <dialog config:type="integer">1</dialog> <element config:type="integer">2</element> <frametitle>Hostname and Domain Name</frametitle> <help>2. Enter the domain name of the server. </help> <question>2. Domain Name</question> <path>networking,dns,domain</path> <default>mydomain.com</default> </ask> </ask-list> -- 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] sled10-sp1 installing -smp and -default kernel for some reason
by Mike Marion 16 Nov '07

16 Nov '07

No <kernel> directive in software setup.. in 99.99% (just guessing) of the cases, the installation does the right thing in determining -default or -smp kernel. In a few rare cases, -default goes on when it shouldn't, haven't been able to determine why. One remote office seeing it happen on a handful of HP xw6400's now, whereas I've only seen it happen when I've been testing in lab, and usually same host installs -smp correctly on a rejump. Logs seem to indicate it's doing the right thing: 2007-11-06 14:27:48 <1> $machine_ip(3655) [YCP] Kernel.ycp:352 ProbeKernel: SMP board 2007-11-06 14:27:48 <1> $machine_ip(3655) [YCP] Kernel.ycp:358 Detected XEN: false 2007-11-06 14:27:48 <1> $machine_ip(3655) [YCP] Arch.ycp:378 stat /proc/xen: $[] 2007-11-06 14:27:48 <1> $machine_ip(3655) [YCP] Kernel.ycp:499 ProbeKernel determined: ["kernel-smp"] Logs show the -smp kernel installing: 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Kernel.ycp:550 Selecting 'kernel-smp' as kernel package 2007-11-06 09:28:01 <1> $machine_ip(3655) [wfm] Kernel.ycp:565 Pkg Builtin called: IsAvailable 2007-11-06 09:28:01 <1> $machine_ip(3655) [wfm] Package.cc(IsAvailable):533 IsAvailable called 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Kernel.ycp:606 Packages for base kernel-smp: ["kernel-smp"] 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Kernel.ycp:640 Computed kernel packages: ["kernel-smp"] 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] AutoinstSoftware.ycp:441 Packages selected in autoinstall mode: ["patch", <SNIP> "kernel-source", "kernel-smp", "yast2-nis-client", "ypbind"] 2007-11-06 09:28:01 <1> $machine_ip(3655) [wfm] AutoinstSoftware.ycp:445 Pkg Builtin called: DoProvide 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] AutoinstSoftware.ycp:445 Installing individual packages: $[] 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Packages.ycp:485 Installation mode packages: [] 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Storage.ycp:4027 AddPackageList have_lvm false mount_lvm false need_evms false 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Storage.ycp:4038 AddPackageList ret [] 2007-11-06 09:28:01 <1> $machine_ip(3655) [YCP] Kernel.ycp:550 Selecting 'kernel-smp' as kernel package 2007-11-06 09:28:01 <1> $machine_ip(3655) [wfm] Kernel.ycp:565 Pkg Builtin called: IsAvailable Later it installs ok: 2007-11-06 09:45:35 <0> $machine_ip(3655) [zypp] ExternalProgram.cc(start_program):172 Executing 'rpm' '--root' '/mnt' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--' '/mnt/var/tmp/AP_0x00000002/suse/x86_64/kernel-smp-2.6.16.46-0.13.x86_64.rpm' 2007-11-06 09:45:35 <0> $machine_ip(3655) [zypp] ExternalProgram.cc(start_program):283 pid 10166 launched 2007-11-06 09:45:41 <0> $machine_ip(3655) [zypp] ExternalProgram.cc(checkStatus):336 pid 10166 successfully completed Then, for some reason, -default installs too: 2007-11-06 09:45:41 <1> $machine_ip(3655) [source] PackageProvider.cc(providePackage):80 provide Package [S1:1][package]kernel-default-2.6.16.46-0.13.x86_64 2007-11-06 09:45:41 <1> $machine_ip(3655) [source] SourceProvideFile.cc(provideFile):99 sourceProvideFile [1]/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm{16.0 M|NoCheckSum} 2007-11-06 09:45:41 <0> $machine_ip(3655) [source] SourceImpl.cc(provideJustFile):510 Going to try provide file /suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm from 1 2007-11-06 09:45:41 <0> $machine_ip(3655) [media] MediaManager.cc(checkDesired):116 checkDesired(1): desired (cached) 2007-11-06 09:45:41 <0> $machine_ip(3655) [media] MediaHandler.cc(provideFile):1008 provideFile(/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm) 2007-11-06 09:45:41 <2> $machine_ip(3655) [source] SourceProvideFile.cc(provideFile):115 No checksum in metadata [1]/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm{16.0 M|NoCheckSum} 2007-11-06 09:45:41 <1> $machine_ip(3655) [source] SourceProvideFile.cc(provideFile):141 sourceProvideFile at /mnt/var/tmp/AP_0x00000002/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm 2007-11-06 09:45:41 <1> $machine_ip(3655) [source] PackageProvider.cc(providePackage):101 provided Package [S1:1][package]kernel-default-2.6.16.46-0.13.x86_64 at /mnt/var/tmp/AP_0x00000002/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm 2007-11-06 09:45:41 <1> $machine_ip(3655) [wfm] SlideShowCallbacks.ycp:253 Pkg Builtin called: TargetUsed 2007-11-06 09:45:41 <1> $machine_ip(3655) [wfm] SlideShowCallbacks.ycp:253 Pkg Builtin called: TargetCapacity 2007-11-06 09:45:41 <1> $machine_ip(3655) [YCP] SlideShow.ycp:1318 Installing kernel-default-2.6.16.46-0.13.x86_64.rpm -- The Standard Kernel 2007-11-06 09:45:41 <1> $machine_ip(3655) [rpm] RpmDb.cc(doInstallPackage):1825 RpmDb::installPackage(/mnt/var/tmp/AP_0x00000002/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm,0) 2007-11-06 09:45:41 <0> $machine_ip(3655) [zypp] ExternalProgram.cc(start_program):172 Executing 'rpm' '--root' '/mnt' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--' '/mnt/var/tmp/AP_0x00000002/suse/x86_64/kernel-default-2.6.16.46-0.13.x86_64.rpm' 2007-11-06 09:45:41 <0> $machine_ip(3655) [zypp] ExternalProgram.cc(start_program):283 pid 10181 launched 2007-11-06 09:45:45 <0> $machine_ip(3655) [zypp] ExternalProgram.cc(checkStatus):336 pid 10181 successfully completed I don't see any indication (some incorrect requirement for -default or something) for why this is triggered. FYI.. the 0.13 kernel version listed is simply our custom kernel, which is just 0.12 with autofs5 patch to autofs4 kernel module, built from the existing src.rpm. We bump rev number for visual verification and so autoyast sees it as newer then the default. Our updates path has versions of this built as -default, -smp, -kdump, -debug and -xen like sles10-sp1 comes with. -- Mike Marion-Unix SysAdmin/Staff IT Engineer-http://www.qualcomm.com Bob: "Ok, I'm goin'... but a swift kick in the ass isn't the solution to everything you know." Red: "I gotta disagree with you there Bob!" -- That 70's show -- 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] apache configuration with sles10 sp1
by Rich 16 Nov '07

16 Nov '07

we are trying to use same autoyast profile created for sles10 for sles10sp1. after solving some minor kernel and nfs issues, an interesting problem with apache has popped up. after autoinstallation process has finished, default-server.conf is empty (0 size). if i now remove apache, then install it again, the file is correctly created. is there some change in autoyast profile needed (i have searched archives, but found nothing), or is there a problem with autoinstallation process ? -- Rich -- 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] Right way to query for install options?
by Lundgren, Andrew 15 Nov '07

15 Nov '07

I am creating an auto install file for machines that will not be using DHCP for network configuration. I would like the installer to query for the IP, netmask and gateway to be used on the box. Anyone have an example of how to do this? If not, what is the best way to go about this? Thanks! -- Andrew Lundgren -- 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] Don't deactivate boot partition
by Bernhard Walle 06 Nov '07

06 Nov '07

Hi, I have the problem that AutoYaST deactivates my boot partition (/dev/sda1) and makes the system unbootable. The setup is following: A partition /dev/sda1 contains a chainloader GRUB. The GRUB is installed in the boot sector of /dev/sda1. The MBR is the generic MBR. The XML file contains <bootloader> <global_entry> <key>serial</key> <value>--unit=0 --speed=57600</value> </global_entry> <global_entry> <key>terminal</key> <value>--timeout=10 serial cons</value> </global_entry> <global> <boot_boot>false</boot_boot> <boot_extended>false</boot_extended> <boot_mbr>false</boot_mbr> <boot_root>true</boot_root> </global> <activate config:type="boolean">false</activate> </bootloader> The root is /dev/sda5. YaST now makes /dev/sda3 (which contains /dev/sda5) as "active". But there's no bootloader. I just want the bootloader configuration module to do *not* activate or deactivate any partitions. This is SLES10-SP1. Any ideas? Thanks, Bernhard -- 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] Pattern file creation...
by Cameron Seader 05 Nov '07

05 Nov '07

Greetings, I am trying to create some Pattern files for add-on media for SLES10 and whenever i try to create one it does not work? I get a message in my y2log when YaST tries to parse it "MultiTag +Prv started before closing +Des". I have checked my Des tag and its closed with -Des: . If i copy a pattern file from the SLES10 media and then modify it, it works just fine. Any Thoughts why? This is very frustrating, about ready to pull my hair out. I have attached my pattern files. The one that works is labeled ZLM_Agent_X-10-7.2.1.i586.pat . TIA, Cameron

2 7

[opensuse-autoinstall] Example of class usage (sles9 sp3)
by Andrew Laden 02 Nov '07

02 Nov '07

I am trying to set up classes for my installations, and cant seem to get the syntax right. Does anyone have any full examples of how to set it up. What I have so far. . ./classes ./classes/Site ./classes/Site/autoinst-site1.xml ./classes/Site/autoinst-site2.xml ./classes/Platform ./classes/Platform/autoinst-DL385.xml ./classes/Base ./classes/Base/autoinst-base.xml ./autoinst-DLx85-site1.xml $ cat autoinst-DLx85-site1.xml <?xml version="1.0"?> <!DOCTYPE profile SYSTEM "/usr/share/autoinstall/dtd/profile.dtd"> <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>Base</class_name> <configuration>autoinst-base.xml</configuration> </class> <class> <class_name>Platform</class_name> <configuration>autoinst-DL385.xml</configuration> </class> <class> <class_name>Site</class_name> <configuration>autoinst-site1.xml</configuration> </class> </classes> </profile> $ cat classes/Platform/autoinst-DL385.xml <?xml version="1.0"?> <!DOCTYPE autoinstall SYSTEM "/usr/share/autoinstall/dtd/classes.dtd"> <autoinstall xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> ..... Whole bunch of hardware specific stuff ..... </autoinstall> Similar for the other class files. I created my class files by splitting out a working profile into components. The profile as a whole works but when I try to do it via classes, the install bombs out when it tries to partition the disk saying that "An error has occurred while trying to create the partitioning plans. Make sure that the contol file has the correct syntax and values" Not sure if I have a syntax issue, or some other problem. Does anyone have a set of working files I can look at to see if I am missing anything? Or any better way to debug this? Some way that I can see if the file is getting merged properly? Thanks -Andrew -- _________________________________________________________ This communication is intended only for the addressee(s) and may contain confidential information. We do not waive any confidentiality by misdelivery. If you receive this communication in error, any use, dissemination, printing or copying is strictly prohibited; please destroy all electronic and paper copies and notify the sender immediately. -- 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] Is there a text-based yast installation?
by Alan McKay 01 Nov '07

01 Nov '07

Hey folks, Is it possible to do a text-based install like there is for Red Hat Anaconda? If so, how do I initiate it? I'm going through the docs but cannot see anything obvious. My problem is that I'm trying to install OpenSuSe 10.2 64bit within a VMWare machine, and it keeps crashing right near the end of the install when it's detecting hardware. I have a hunch that doing a text-based install would fix this, based on the stuff happening with the virtual screen at that time. thanks, -Alan -- "Aikido has but one principle - the universal reality of life" - Mitsugi Saotome -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2