- openSUSE Autoinstall

[opensuse-autoinstall] SLES11 SP2
by Mario Gzuk 20 Jul '12

20 Jul '12

Hi, I use the following option to set a releay host: <outgoing_mail_server>test.com</outgoing_mail_server> For SP1 it is working fine, but with SP2 the relay_host in the postfix main.cf isnt set any more. Also the alias config: <aliases config:type="list"> <alias> <alias>root</alias> <comment></comment> <destinations>bla(a)blub.com</destinations> </alias> </aliases> is written, but the "newaliases" command seems not to be executed after the alias is set. mail to root will be sent local, after running newaliases the mail is send to bla(a)blub.com. Thank you for an answer. Cheers Mario -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 9

[opensuse-autoinstall] opensuse 11.4: Order of packages to install
by Daniel Spannbauer 20 Jul '12

20 Jul '12

Hello, we install a 11.4-system with autoyast. Works nearly perfectly. But now, I have a problem and don't know how to solve it.... There are several packages which generate users with fixed IDs.And there is one package (not from us) which creates a user without a fixed ID. So the user gets the next free uid. In most cases it works, but sometimes the package with the random uid is installed before our packages with the fixed uid. In this case the uid already exists when our package is installed and yast shows an error and stops here....our user is not created. Which order are the packages installed? Are they installed randomly? Any Ideas how to solve it? Regards Daniel -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 4

[opensuse-autoinstall] autoyast 12.2 factory troubles: cannot find /usr/bin/xsltproc
by Matthias Danzl 20 Jul '12

20 Jul '12

Trying to set up autoyast for the 12.2 development version, I encountered the error stating autoyast can't find /usr/bin/xsltproc during execution of pre-installation scripts. Using the command line, I found out that xsltproc is nowhere in $PATH. Any ideas on this? TIA -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 11

[opensuse-autoinstall] Installation: Can't configure net with "linuxrc"
by Dominik Baumann 16 Jul '12

16 Jul '12

Hello, for using autoyast per http i want to configure network with linuxrc [1] and its kernel boot parameters (hostip, netmask, ...), resp. with the appropriate installation dialogue [2]. Unfortunately both don't work for me: The machine doesn't react to ping nor is "ifconfig -a" showing an active network interface or ip address. But i can set it manually with "ifconfig eth0 inet ..." at the same phase of installation, so missing network drivers shouldn't be the problem. The problem appears both on opensuse release 12.1 and 12.2/Milestone-3, both in a virtual and a physical machine. Any hints? PS: I know that linuxrc hasn't directly to do with autoyast, but perhaps it's often used there(?). I already asked at the german opensuse-de@ mailing list, but found no solution there. Dominik. [1] http://en.opensuse.org/SDB:Linuxrc [2] http://paste.opensuse.org/6379e182 http://paste.opensuse.org/af7f337d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 18

[opensuse-autoinstall] proxy and suse_register/smt problem (and workaround)
by Oliver Gorwits 09 Jul '12

09 Jul '12

Hi, (I'm new to SuSE & AutoYaST, and not sure whether this is a problem with AutoYaST, or a SuSE package, or my own mistake...) I noticed that configuring both <proxy> and <suse_register> in an autoyast profile fails if <no_proxy> is needed to access the SMT server. What seems to happen is that the <proxy> section of the autoyast profile is parsed, but the root user's .curlrc file only gets the --proxy setting and not any --noproxy setting. This makes SMT registration fail. A workaround is to have a script like this in the autoyast profile: <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <source><![CDATA[ echo "--noproxy 'localhost,.example.com'" >> /root/.curlrc ]]> </source> </script> </chroot-scripts> So, this message is partly for the benefit of people searching the list archives, but also an open question whether anyone else is aware of the problem. For info, I am installing from a SLES 11 SP2 DVD, and the suseRegister package version is 1.4-1.24.1. regards, oliver. -- Oliver Gorwits Networks and Computer Security ECMWF -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

[opensuse-autoinstall] 12.1, autoyast and systemd
by 686f6c6d 04 Jul '12

04 Jul '12

Hi, here's the problems I ran into. They all seem to be related to systemd, but I did not want to hijack the other thread, although this one might solve the other problem, too. 1. The final kexec/reboot is not executed. Both <final_reboot config:type="boolean">false</final_reboot>, meaning kexec will be used, and <final_reboot config:type="boolean">true</final_reboot> have no effect at all[0]. This also means that... 2. Init-Services (<runlevel>) defined in autoyast are not started/stopped, so, f.e., no ssh keys are generated. (This also results in a lot of subsequent errors in our setup.) To fix this, just include: <software> <remove-packages config:type="list"> <package>systemd-sysvinit</package> </remove-packages> </software> This way, sysvinit-init will be installed and used. When can we expect autoyast to support systemd? [0]: Once you do a manual reboot (if you happen to have access other than ssh to the machine), the machine will do the autoyast kexec/reboot after that. -- Kind regards/Mit freundlichen Grüßen Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

5 20

[opensuse-autoinstall] partitioning and skiplist
by Jochen Schaefer 03 Jul '12

03 Jul '12

Hi, I want to prevent the partitioning of all /dev/sdxxx devices by autoyast. How to achieve that? Regarding to Uwe's blog I can use the skip_list feature. But I'm uncertain about which skip_key and skip_value to use? Thanks, Jochen -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 4

[opensuse-autoinstall] Copy directories from remote source using <file_location>
by Joschi Brauchle 02 Jul '12

02 Jul '12

Hi there, I just wanted to check before I do a trial and error test... Autoyast's file section currently allows me to: * Fetch files from remote source using <file_location>http://my.server.site/issue</file_location> for example. * Create directories by adding a slash, i.e., <file_path>/mydir/a/b/c/</file_path> So, natural question: Can Autoyast fetch directories by combining both? <file_location>http://my.server.site/issue/</file_location> <file_path>/mydir/a/b/c/</file_path> If not, I will use a script to do that... but it would be nice :-) -- Dipl.-Ing. Joschi Brauchle, M.S. Institute for Communications Engineering (LNT) Technische Universitaet Muenchen (TUM) 80290 Munich, Germany Tel (work): +49 89 289-23474 Fax (work): +49 89 289-23490 E-mail: joschi.brauchle(a)tum.de Web: http://www.lnt.ei.tum.de/

2 1

[opensuse-autoinstall] ldap-configuration using ldap
by Robert Klein 02 Jul '12

02 Jul '12

Hi, I'm currently testing ldap-client configuration using autoyast. Here is a list of issues I found. Please comment. I'll probably file some bug reports next week. Testing system is factory snapshot from April 12, 2012 (that is, M3, probably). - (YaST) Issues during installation: - Both the reference profile and the XML schema allow the parameter <bind_dn>, but there's no binddn in /etc/ldap after installation. - missing support for additional LDAP configuration parameters, for example there ought to be a parameter <bind_pw> resulting in a bindpw in /etc/ldap.conf after installation. Also, I could use a way wo put the tls certfile into the autoyast xml, e.g. using a parameter <tls_cacertfile-content><source><![CDATA[...]]></... - Yast Reference Profile (created using Yast -> Autoyast -> Tools -> Create Reference Profile) issues: - A created reference profile has a parameter <mkhomedir>, but it isn't allowed according to the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) and apparently isn't used, i.e. it didn't appear in /etc/ldap.conf after installation (I only had it set to "false", though). - schema only issues: - The parameters <sssd>, <tls_cacertdir> and <tls_cacertfile> aren't in the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) They are, however reference profiles created with Yast -> AutoYast and are used during installation Thanks and best regards Robert -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 3

[opensuse-autoinstall] 11.4: Problem with postinstallscript for fixing the second-stage-bug
by Daniel Spannbauer 26 Jun '12

26 Jun '12

Hello, I try to install a system opensuse 11.4 with autoyast. To "fix" the rpmcopy_secondstage_bug I run the following script in chroot: --------------------------------------- <script>  <chrooted config:type="boolean">true</chrooted> <filename>fix_postinstall_bug.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/bash ( while [ ! -f /var/lib/YaST2/installation_disabled_steps ]; do sleep 1 done cp /var/lib/YaST2/installation_disabled_steps /var/lib/YaST2/installation_disabled_steps.bkp cat /var/lib/YaST2/installation_disabled_steps.bkp | grep -v "rpmcopy_secondstage" > /var/lib/YaST2/installation_disabled_steps) &]]> </source> </script> --------------------------------------------------------- The script is called during the installation but it seems that it is abborted before the file installation_disabled_steps is generated. The log shows: ------------------------------ 2012-06-05 04:48:10 <1> instze32(3283) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Calling YaST client autoinst_scripts2_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/autoinst_scripts2_finish.ycp:33 starting autoinst_scripts2_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] AutoinstScripts.ycp:715 Writing chroot script into /var/adm/autoinstall/scripts/fix_postinstall_bug.sh 2012-06-05 04:48:10 <1> instze32(3283) [YCP] AutoinstScripts.ycp:766 Script Execution command: /bin/sh -x /var/adm/autoinstall/scripts/fix_postinstall_bug.sh 2&> /var/adm/autoinstall/logs/fix_postinstall_bug.sh.log 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/autoinst_scripts2_finish.ycp:58 autoinst_scripts2_finish finished 2012-06-05 04:48:10 <1> instze32(3283) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Called YaST client returned. 2012-06-05 04:48:10 <1> instze32(3283) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2012-06-05 04:48:10 <1> instze32(3283) [Interpreter] clients/installation_settings_finish.ycp:108 Calling YaST client installation_settings_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/installation_settings_finish.ycp:29 starting installation_settings_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/installation_settings_finish.ycp:44 Writing disabled modules ["system_analysis", "update_partition_auto", "add-on", "productsources", "user", "user_non_interactive", "auth", "initialization", "netprobe", "rpmcopy_secondstage", "hostname", "ask_net_test", "do_net_test", "addon_update_sources", "extrasources", "ask_online_update", "you", "restore_settings", "release_notes", "save_hardware_status", "congratulate", "lan", "disks_activate"] into /var/lib/YaST2/installation_disabled_steps --------------------------------------- Any hints about that? Regards Daniel + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 ---------------------------------- Thats all..... In y2log you can see that the installaion_disabled_steps is generated after the scripts can do their job.... ------------------------------- -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 5