- openSUSE Autoinstall

[opensuse-autoinstall] Yast?
by Erico Mendonça 11 Sep '10

11 Sep '10

I didn't know YaST could do that... http://www.yast.com :) -- -- Erico -- 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] Splitting a SUSE install
by Erico Mendonça 10 Sep '10

10 Sep '10

I currently have a pretty elaborate AutoYAST-based SLE installation, and the image size is now over 3GB. It installs fine via DVD (and network), but now I need it to be split among CDs. What would be the best way to automatically split it into CD images? I was hoping the recent announcement on SuSE Studio importing AutoYAST profiles would help me, but my setup's partitioning scheme is determined at install time. Apparently this isn't supported in SuSE Studio? -- -- Erico -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] boolean values in ask scripts broken in SLES 11 SP1
by Andrew Daugherity 31 Aug '10

31 Aug '10

On Tue, 2010-08-31 at 11:05 +0200, Uwe Gansert wrote: > on Monday 30 August 2010 Andrew Daugherity wrote: > > Can you please test the attached driverupdate for 1st and 2nd stage? > > Works great, thanks! -- Andrew Daugherity <adaugherity(a)tamu.edu> Texas A&M University -- 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] cd:/driverupdate: File not Signed
by Nicholas Betcher 31 Aug '10

31 Aug '10

Hello, I'm writing because after creating an Image+ISO and booting it, Linuxrc comes up right before YaST and throws a warning stating: cd:/driverupdate: File not signed. If you really trust your repository, you may continue in an insecure mode. (screenshot at: http://www.nickbetcher.com/~nbetcher/Linuxrc error.png ) I didn't include any driver updates, nor ask for any. Also, this message is unaffected by the settings to skip error/warning/info messages and demands for user intervention to proceed with auto-install. Is there any way to get this message to not appear, ideally through my AutoYaST config file. Thanks! Nick Betcher -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 3

Re: [opensuse-autoinstall] boolean values in ask scripts broken in SLES 11 SP1
by Andrew Daugherity 31 Aug '10

31 Aug '10

On Mon, 2010-08-30 at 17:34 +0200, Uwe Gansert wrote: > on Thursday 26 August 2010 Andrew Daugherity wrote: > > > somewhere. Can this be fixed with a driver update? > > I just noticed that you are using stage=cont. > Then a driverupdate might not be the best way to fix that. > I could send you a RPM if that helps you? You'd have to install that then via > add-on for example. > Would that be an option for you? > I think I'd need both then to truly fix this, although the second stage problem (registration) is the one I care about... let me see if I understand correctly: * to fix a problem in the first stage, I need a driver update * to fix something in the second stage (post-reboot), I need an updated RPM installed in the first stage? (As an aside, I guess this would be the way to fix the "keep_install_network loses DNS and routes bug" described at http://hedgehogpainter.livejournal.com/7022.html ?) Since you can't set repo priorities in autoyast (that I know of) would it pick up this package from my local YUM repo (instead of the one from sles11-sp1-pool) if it had a higher version? Thanks, -- Andrew Daugherity Systems Analyst Division of Research & Graduate Studies Texas A&M University -- 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] ask workarround sles10 pathlist
by Jochen Schaefer 30 Aug '10

30 Aug '10

Hi, I'm looking for a workarround to implement the pathlist feature for sles10. pathlist is available since code 11 only. Until now I have to configure 3 ask secttions to retrieve the same password for 3 different pathes. I'm wondering at which point in time ask popups arrive in stage 1. If I could change modified.xml with the script feature within ask then it would be a working approach. But if ask popups come into place after yast reads modified.xml this approach will fail. Thanks for any hints, Jochen -- 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] boolean values in ask scripts broken in SLES 11 SP1
by Andrew Daugherity 30 Aug '10

30 Aug '10

I have a working autoyast config I use for installing SLES 11. It works for SLES11 SP1 too, except for customer center registration. Comparing y2log between sp1 and orig. sles11, I see that this is because the boolean values from my ask script are not being parsed correctly. do_register is set to false in my autoyast profile, but can be overridden by an ask dialog. Register section: <suse_register> <do_registration config:type="boolean">false</do_registration> <register_regularly config:type="boolean">true</register_regularly> <submit_hwdata config:type="boolean">true</submit_hwdata> <submit_optional config:type="boolean">true</submit_optional> <registration_data> <email>suseupdates(a)XXXX.tamu.edu</email> <moniker>foo</moniker> <regcode-sles>00000000000000</regcode-sles> </registration_data> </suse_register> 'moniker' and 'do_registration' are overridden by an ask script: <general> <ask-list config:type="list">  <ask> <title>Novell Customer Center configuration</title> <pathlist config:type="list"> <path>suse_register,do_registration</path> </pathlist> <question>Register this system with Novell?</question> <stage>cont</stage> <type>boolean</type> <default config:type="boolean">false</default> <dialog config:type="integer">2</dialog> <element config:type="integer">0</element> </ask> <ask> <pathlist config:type="list"> <path>suse_register,registration_data,moniker</path> </pathlist> <question>System Name (prefix with 'rgs-' if name is generic)</question> <stage>cont</stage> <dialog config:type="integer">2</dialog> <element config:type="integer">1</element> <script> <rerun_on_error config:type="boolean">true</rerun_on_error> <feedback config:type="boolean">true</feedback> <debug config:type="boolean">false</debug> <environment config:type="boolean">true</environment> <source><![CDATA[ if [ -z "$VAL" ]; then echo "Please set the system name."; exit 1; fi exit 0 ]]> </source> </script> </ask> <ask> <pathlist config:type="list"> <path>software,do_online_update</path> </pathlist> <question>Run online update (requires registration)?</question> <stage>cont</stage> <type>boolean</type> <default config:type="boolean">false</default> <dialog config:type="integer">2</dialog> <element config:type="integer">2</element> </ask> </ask-list>  </general> This presents a dialog with a checkbox for "Register this system with Novell?" (default unchecked), applied to 'do_registration'; a text field for the hostname (applied to 'moniker'), and another checkbox for running updates afterwards. It works great in SLES 11. In SP1, however... Here are the sections of y2log relating to registration. Note the errors regarding boolean values. 2010-08-26 06:58:11 <1> linux(3903) [YCP] clients/inst_autopost.ycp:91 current resource: suse_register 2010-08-26 06:58:11 <1> linux(3903) [YCP] clients/inst_autopost.ycp:103 Importing configuration for customer_center 2010-08-26 06:58:11 <1> linux(3903) [YCP] clients/inst_autopost.ycp:136 Calling auto client with: $["do_registration":"true", "register_regularly":true, "registration_data":$["email":"suseupdates@XXXX", "moniker":"imsweb3", "regcode-sles":"XXXX"], "submit_hwdata":true, "submit_optional":true] 2010-08-26 06:58:11 <1> linux(3903) [wfm] Y2WFMComponent.cc(import):749 Y2WFMComponent::import (Register) 2010-08-26 06:58:12 <2> linux(3903) [Parser] clients/suse_register_auto.ycp:71 Warning: Format string is not constant, no parameter checking possible 2010-08-26 06:58:12 <1> linux(3903) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2010-08-26 06:58:12 <1> linux(3903) [Interpreter] clients/suse_register_auto.ycp:481 Calling YaST client suse_register_auto (arguments: ["Import", $["do_registration":"true", "register_regularly":true, "registration_data":$["email":"suseupdates@XXXX", "moniker":"imsweb3", "regcode-sles":"XXXX"], "submit_hwdata":true, "submit_optional":true]]) 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:417 ---------------------------------------- 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:418 suse_register_auto started 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:432 func=Import 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:433 param=$["do_registration":"true", "register_regularly":true, "registration_data":$["email":"suseupdates@XXXX", "moniker":"imsweb3", "regcode-sles":"XXXX"], "submit_hwdata":true, "submit_optional":true] 2010-08-26 06:58:12 <1> linux(3903) [YCP] Register.ycp:91 running with user id $["exit":0, "stderr":"", "stdout":"0\n"] 2010-08-26 06:58:12 <3> linux(3903) [Interpreter] Register.ycp:1626 Can't convert value '"true"' to type 'boolean' 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:479 ret=true 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:480 suse_register_auto finished 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:481 ---------------------------------------- 2010-08-26 06:58:12 <1> linux(3903) [Interpreter] clients/suse_register_auto.ycp:481 Called YaST client returned. 2010-08-26 06:58:12 <2> linux(3903) [Parser] clients/suse_register_auto.ycp:71 Warning: Format string is not constant, no parameter checking possible 2010-08-26 06:58:12 <1> linux(3903) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2010-08-26 06:58:12 <1> linux(3903) [Interpreter] clients/suse_register_auto.ycp:481 Calling YaST client suse_register_auto (arguments: ["Packages"]) 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:417 ---------------------------------------- 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:418 suse_register_auto started 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:432 func=Packages 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:433 param=$[] 2010-08-26 06:58:12 <1> linux(3903) [YCP] Register.ycp:245 Checking if this machine is a XEN instance or host. 2010-08-26 06:58:12 <1> linux(3903) [YCP] Arch.ycp:390 stat /proc/xen: $["atime":1282823892, "ctime":1282823892, "gid":0, "inode":4026531950, "isblock":false, "ischr":false, "isdir":true, "isfifo":false, "islink":false, "isreg":false, "issock":false, "mtime":1282823892, "nlink":2, "size":0, "uid":0] 2010-08-26 06:58:12 <1> linux(3903) [YCP] Arch.ycp:396 /proc/xen exists 2010-08-26 06:58:12 <1> linux(3903) [YCP] Arch.ycp:405 Kernel version: 2.6.32.12-0.7-xen 2010-08-26 06:58:12 <1> linux(3903) [YCP] Arch.ycp:413 kernel-xen is running: true 2010-08-26 06:58:12 <1> linux(3903) [YCP] Register.ycp:249 XEN enabled. Now detecting type. 2010-08-26 06:58:12 <1> linux(3903) [YCP] Arch.ycp:430 stat /proc/xen/xsd_port: $[] 2010-08-26 06:58:12 <1> linux(3903) [YCP] Register.ycp:258 Detected XENU 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:134 Registration suggests the following package changes: $["install":["xen-tools-domU"], "remove":["xen-tools"]] 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:479 ret=$["install":["xen-tools-domU"], "remove":["xen-tools"]] 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:480 suse_register_auto finished 2010-08-26 06:58:12 <1> linux(3903) [YCP] clients/suse_register_auto.ycp:481 ---------------------------------------- 2010-08-26 06:58:12 <1> linux(3903) [Interpreter] clients/suse_register_auto.ycp:481 Called YaST client returned. [snip] 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/inst_autoconfigure.ycp:137 current resource: suse_register 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/inst_autoconfigure.ycp:148 Writing configuration for customer_center 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/inst_autoconfigure.ycp:183 Calling auto client with: $["do_registration":"true", "register_regularly":true, "registration_data":$["email":"suseupdates@XXXX", "moniker":"imsweb3", "regcode-sles":"XXXX"], "submit_hwdata":true, "submit_optional":true] 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/inst_autoconfigure.ycp:40 current step: 7 2010-08-26 06:58:36 <2> imsweb3(3903) [Parser] clients/suse_register_auto.ycp:71 Warning: Format string is not constant, no parameter checking possible 2010-08-26 06:58:36 <1> imsweb3(3903) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2010-08-26 06:58:36 <1> imsweb3(3903) [Interpreter] clients/suse_register_auto.ycp:481 Calling YaST client suse_register_auto (arguments: ["Write"]) 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:417 ---------------------------------------- 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:418 suse_register_auto started 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:432 func=Write 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:433 param=$[] 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] Register.ycp:91 running with user id $["exit":0, "stderr":"", "stdout":"0\n"] 2010-08-26 06:58:36 <3> imsweb3(3903) [Interpreter] Register.ycp:1644 'if (Register::do_registration)' evaluates to non-boolean 'nil' (VOID). 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] Register.ycp:91 running with user id $["exit":0, "stderr":"", "stdout":"0\n"] 2010-08-26 06:58:36 <2> imsweb3(3903) [YCP] Progress.ycp:260 Deprecated function. Use Progress::set instead 2010-08-26 06:58:36 <2> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:465 Progress::on () 2010-08-26 06:58:36 <2> imsweb3(3903) [YCP] clients/inst_autoconfigure.ycp:194 Call::Function (module_auto, ["Write"]) 2010-08-26 06:58:36 <2> imsweb3(3903) [YCP] ProductControl.ycp:1499 ProductControl::RunFrom (0, false) 2010-08-26 06:58:36 <2> imsweb3(3903) [YCP] clients/inst_worker_continue.ycp:117 ProductControl::Run () 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:479 ret=true 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:480 suse_register_auto finished 2010-08-26 06:58:36 <1> imsweb3(3903) [YCP] clients/suse_register_auto.ycp:481 ---------------------------------------- 2010-08-26 06:58:36 <1> imsweb3(3903) [Interpreter] clients/suse_register_auto.ycp:481 Called YaST client returned. In the first segment we have "Can't convert value '"true"' to type 'boolean'" and then in the second " 'if (Register::do_registration)' evaluates to non-boolean 'nil' ". This does not happen in the logs of sles11 pre-sp1. I think it's a problem handling boolean values from ask scripts in general, rather than something with the registration module, as I see a similar error from my other ask dialog (controlling dhcp_hostname): 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:14 ---------------------------------------- 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:15 Lan autoinst client started 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:292 keep_install_network is enabled 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:307 DNS and routing defined in AY profile, will use it 2010-08-26 06:58:14 <1> linux(3903) [YCP] LanUdevAuto.ycp:53 nothing changed, eth0 is old style dev_name 2010-08-26 06:58:14 <3> linux(3903) [Interpreter] clients/lan_auto.ycp:162 Can't convert value '"false"' to type 'const boolean' 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:173 input=$["config":$["dhcp":$["DHCLIENT_SET_HOSTNAME":nil]], "devices":$["eth":$["eth0":$["BOOTPROTO":"dhcp", "STARTMODE":"auto", "USERCONTROL":"no"]]], "dns":$["dhcp_hostname":"false", "domain":"vpr.int", "hostname":"imsweb3", "resolv_conf_policy":"auto"], "hwcfg":$[], "interfaces":[$["bootproto":"dhcp", "device":"eth0", "startmode":"auto", "usercontrol":"no"]], "keep_install_network":true, "managed":false, "routing":$["ip_forward":false], "start_immediately":true] 2010-08-26 06:58:14 <1> linux(3903) [YCP] NetworkInterfaces.ycp:1458 List( ) = ["eth0"] 2010-08-26 06:58:14 <3> linux(3903) [Interpreter] DNS.ycp:352 Can't convert value '"false"' to type 'const boolean' 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:131 write_hostname_to_hosts default value: false 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:382 DNS Import: 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:383 nameservers=[] 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:384 searchlist=[] 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:385 hostname=imsweb3 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:386 domain=vpr.int 2010-08-26 06:58:14 <1> linux(3903) [YCP] DNS.ycp:387 dhcp_hostname=nil, write_hostname=false 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:358 Lan auto finished 2010-08-26 06:58:14 <1> linux(3903) [YCP] clients/lan_auto.ycp:359 ---------------------------------------- Note the "can't convert false to const boolean" and later "dhcp_hostname=nil". Looks live I've found an autoyast bug, unless I missed a syntax change somewhere. Can this be fixed with a driver update? Andrew Daugherity Systems Analyst Division of Research & Graduate Studies Texas A&M University -- 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] Bad grub menu after autoyast install
by Eric Rothweiler 27 Aug '10

27 Aug '10

We use a pretty simple AutoYast that simply lays down the same basic install and partitioning using ASK only to pick up IP (address, mask, & gateway) and HOSTNAME info. We come back afterwards to install OES2 on top of SLES. We started this with OES2 (no SP) and have just finally started new installs of OES2 SP2 (SLES 10 SP3). One thing that has been consistent in SP2 and, unfortunately, now SP3 is the grub menu referencing the kernel from one SP earlier. For example, 2.6.16.60-0.21 is now being referenced in the SP3 grub menu after AutoYast installation (the installed kernel is 0.54.5). It doesn't do this every time and I have been unable to find a pattern to the problem appearing. Hoping someone knows why it would be doing this. However, I am willing to do a workaround on this but I'm not a coder by nature and have hit roadblocks figuring out how to include AutoYast code to copy a "standard" grub menu from my install DVD. If anyone could point me to the way to insert this type of code into my AutoYast I would be content. Thanks! Eric -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 5

[opensuse-autoinstall] SLES 11 SP1 x86_64 invalid root filesystem after autoyast install
by justin.kinney＠academy.com 23 Aug '10

23 Aug '10

Hello all, I'm having a strange problem while trying to use the same autoyast I used for SLES 11 on SLES 11 SP1. I didn't think there would be any compatibility issues, but maybe there is? The problem is that during the second stage of install, after the first reboot, the boot process stops (while still in initrd) and drops me to a shell. When I exit the shell (control-D), the boot process continues and everything is fine. The system functions completely normally after boot. I've engaged Novell support, but so far we have not found a resolution. However, I followed the suggestion of manually installing a machine and then using the cloned autoinst.xml as a starting point. Every time I build a box with that autoyast file, I do not see this issue. I've looked and looked, but cannot find the issue, or any significant difference between my autoyast and the cloned system's autoyast. I've attached both here. Can anybody see something I'm overlooking? There are two files below. The first (autoinst.xml) is a clone of the manually installed system which always works. The second (autoyast_slspgen06e.xml) is the slightly modified SLES 11 autoyast file that produces the invalid root filesystem problem. Also a few screenshots (edited to include an index dot): Thanks in advance, Justin

2 5

[opensuse-autoinstall] AutoYaST goes Twitter
by Uwe Gansert 21 Aug '10

21 Aug '10

Hi, well, it's not that it can read XML files from a twitter feed now ;) but after the blog(*), starting from today, AutoYaST goes one further step to web 2.0 and has it's own twitter account (**). It's not for great hints or enhanced support or so. It's just a little look behind the curtain of my life with AutoYaST ... for those who care ;) And it seems you can't do any bigger project these days without something like a blog, twitter or facebook or ... so ... here it is. (*) http://ugansert.blogspot.com (**) http://twitter.com/autoyast ciao, Uwe Gansert Uwe Gansert, Server Technologies Team SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2