- openSUSE Autoinstall

[opensuse-autoinstall] Feature: Add <location> tag to <file_script> to get file script from remote location
by Joschi Brauchle 08 May '13

08 May '13

Hi, I have a pretty long bash script as a <file_script>, modifying one of the files provided via <file>. I tried to move the script source out of the XML file by using a <location> tag instead of the <source> inside the <file_script>. But it looks like this is not supported yet...would be nice to have though! Best regards, J Brauchle

4 6

[opensuse-autoinstall] Problems running on startup a service created in a postinstall script in 12.3
by Rainer Krienke 17 Apr '13

17 Apr '13

Hello, to automatically install a openSuSE 12.3 desktop client that fits into our network environment I need to change several configs uopn installtion so little manual postinstallation is needed afterwards. I do this using an autoyast installation that includes a postinstall script. This used to work fine until systemd came up. In openSuSE 12.3 I create a service file /lib/systemd/system/lfinalinstall that looks like this: ------------------ [Unit] Description=lfinalinstall install script After=apparmor.service local-fs.target network.service Before=xdm.service [Service] Type=oneshot Environment=SYSTEMD_NO_WRAP=1 TERM=linux ExecStart=$LSCRIPT RemainAfterExit=yes TimeoutSec=0 StandardInput=tty [Install] WantedBy=default.target ----------------- Next I run "/bin/systemctl enable lfinalinstall" and finally I run "systemctl daemon-reload" After the postinstall scripts of autoyast have been executed my script lfinalinstall is actually beeing started. The problem is that it depends on a running network, but the interface eth0 is still unconfigured (no dhcpcd is running for it yet, no ip assigned) at this time and so my script cannot do the job its supposed to do and fails. After a manual reboot thisngs work. Does anyone have an idea what I have to do to have the finalinstall service started when network is available? The dependency on network.service seems not to work for me. Thanks Rainer Krineke -- Rainer Krienke, Uni Koblenz, Rechenzentrum, A22, Universitaetsstrasse 1 56070 Koblenz, http://userpages.uni-koblenz.de/~krienke, Tel: +49261287 1312 PGP: http://userpages.uni-koblenz.de/~krienke/mypgp.html,Fax: +49261287 1001312

2 2

[opensuse-autoinstall] post-packages sles vs sled
by Mike Marion 03 Apr '13

03 Apr '13

On 11.2 at least, it seems like post-packages works fine for sles, but is completely ignored on sled installs. I've done some testing and am seeing no mention of autoyast even looking at post-packages on the sled installs. Is this a known difference? I saw another thread mentioning a known issue with opensuse 11.4 but that wouldn't explain why sles works and not sled. We have a package that mostly creates links, fun stuff like: /usr/lib64/libXaw3d.so.7 -> libXaw3d.so.8.0 for issues with older tools we still need to support. Rather then deal with trying to make sure dependencies are listed in the rpm itself to ensure the installation order, we just use the post-packages bit. Otherwise it would sometimes install before even the paths existed and would get wiped out by later rpm installs. This problem didn't seem to exist with sles/sled 10.x (for sure 10.4 that I've gone back and tested). -- Mike Marion-Unix SysAdmin/Sr. Staff IT Engineer-http://www.qualcomm.com O'Neill: "I hope you like Guinness sir. I find it a refreshing substitute for... food." ==> Stargate SG-1 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 3

[opensuse-autoinstall] openSUSE 12.3 installation with updates from DVD
by Stephen Fergusson 01 Apr '13

01 Apr '13

Hi all, We have downloaded the openSUSE 12.3 X64 DVD and copied it to a USB pendrive and OK installing from the USB pendrive. We have just downloaded the 1.2GB's of updates from ftp-1.gwdg.de/pub/linux/suse/opensuse/update/12.3 that have been released since the release of 12.3. Is it possible to incorporate these updates onto the USB (or DVD) and get those installed in the initial installation? I have read the information at SUSE / Uwe Gansert / autoyast / autoinstall and used the tool "create_update_source.sh" which has added the updates folder to the USB pendrive but what do I have to do next to tell the install to use this update folder? Have been playing with autoyast and got a profile that nearly works so if it is something that gets added in the autoinst.xml, then that should be OK. I am aware of the ag_initscripts issue with autoyast as described here... [Bug 801878] AutoYast hangs at "Install Required Packages" and waits for. Any help or advise appreciated. Regards, Stephen. PS. Please note... I have also posted this on the openSUSE forums. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 3

[opensuse-autoinstall] Re: openSUSE 12.3 installation with updates from DVD
by Stephen Fergusson 27 Mar '13

27 Mar '13

Hi all, We have downloaded the openSUSE 12.3 X64 DVD and copied it to a USB pendrive and OK installing from the USB pendrive. We have just downloaded the 1.2GB's of updates from ftp-1.gwdg.de/pub/linux/suse/opensuse/update/12.3 that have been released since the release of 12.3. Is it possible to incorporate these updates onto the USB (or DVD) and get those installed in the initial installation? I have read the information at SUSE / Uwe Gansert / autoyast / autoinstall and used the tool "create_update_source.sh" which has added the updates folder to the USB pendrive but what do I have to do next to tell the install to use this update folder? Have been playing with autoyast and got a profile that nearly works so if it is something that gets added in the autoinst.xml, then that should be OK. I am aware of the ag_initscripts issue with autoyast as described here... [Bug 801878] AutoYast hangs at "Install Required Packages" and waits for. Any help or advise appreciated. Regards, Stephen. PS. Please note... I have also posted this on the openSUSE forums. -- 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] SUSE-12.3 weirdness
by Lonni J Friedman 26 Mar '13

26 Mar '13

I'm trying to get autoyast working with OpenSUSE-12.3. The actual OS installation seems to work fine, but after the reboot (when it does a bunch of post-install stuff), its consistently hanging at: Preparing System for Automatic Instlallation Install required packages Checking for packages required for runlevel ---> 33% Or more accurately, it just stalls. The system isn't hung, I can switch between virtual consoles, but the actual installation never progresses at all. Load is 0.00. I started poking around in the newest log in /var/log/Yast2, and I see the following at the bottom of y2log: ########## 2013-03-06 05:33:47 <1> dhcp-172-16-170-244(3533) [Interpreter] network/services/host.ycp:405 Calling YaST client lan_auto 2013-03-06 05:33:47 <1> dhcp-172-16-170-244(3533) [YCP] network/lan/wizards.ycp:34 ---------------------------------------- 2013-03-06 05:33:47 <1> dhcp-172-16-170-244(3533) [YCP] network/lan/wizards.ycp:35 Lan autoinst client started 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] LanUdevAuto.ycp:110 nothing changed, eth0 is old style dev_name 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] network/lan/wizards.ycp:195 input=$["config":$["dhcp":$["DHCLIENT_SET_HOSTNAME":true]], "devices":$["eth":$["eth0":$["BOOTPROTO":"dhcp", "STARTMODE":"onboot"]]], "dns":$["dhcp_hostname":true, "dhcp_resolv":true, "domain":"local", "hostname":"linux"], "hwcfg":$[], "interfaces":[$["bootproto":"dhcp", "device":"eth0", "startmode":"onboot"]], "start_immediately":true] 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:151 write_hostname_to_hosts default value: false 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:388 DNS Import: 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:389 nameservers=[] 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:390 searchlist=[] 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:391 hostname=linux 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:392 domain=local 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] DNS.ycp:393 dhcp_hostname=true, write_hostname=false 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] NetworkService.ycp:134 NetworkManager: false 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/lan_auto.ycp:404 Lan auto finished 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/lan_auto.ycp:405 ---------------------------------------- 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [Interpreter] network/services/host.ycp:405 Called YaST client returned. 2013-03-06 05:33:48 <2> dhcp-172-16-170-244(3533) [Parser] network/widgets.ycp:205 Warning: Format string is not constant, no parameter checking possible 2013-03-06 05:33:48 <2> dhcp-172-16-170-244(3533) [Parser] network/lan/address.ycp:101 Warning: Format string is not constant, no parameter checking possible 2013-03-06 05:33:48 <2> dhcp-172-16-170-244(3533) [Parser] network/services/host.ycp:60 Warning: Format string is not constant, no parameter checking possible 2013-03-06 05:33:48 <2> dhcp-172-16-170-244(3533) [Parser] network/services/host.ycp:384 Warning: Format string is not constant, no parameter checking possible 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [Interpreter] network/services/host.ycp:405 Calling YaST client lan_auto 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] network/lan/wizards.ycp:34 ---------------------------------------- 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] network/lan/wizards.ycp:35 Lan autoinst client started 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/lan_auto.ycp:404 Lan auto finished 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/lan_auto.ycp:405 ---------------------------------------- 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [Interpreter] network/services/host.ycp:405 Called YaST client returned. 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: ldap 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: mail 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: modem 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: nfs 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: nis 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: ntp-client 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: printer 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: proxy 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: remote 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: restore 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:112 current resource: runlevel 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:124 Importing configuration for runlevel 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/inst_autopost.ycp:157 Calling auto client with: $["default":"3"] 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [wfm] Y2WFMComponent.cc(import):771 Y2WFMComponent::import (RunlevelEd) 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [wfm] Y2WFMComponent.cc(import):771 Y2WFMComponent::import (Systemd) 2013-03-06 05:33:48 <2> dhcp-172-16-170-244(3533) [Parser] runlevel/ui.ycp:740 Warning: Format string is not constant, no parameter checking possible 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [Interpreter] runlevel/ui.ycp:117 Calling YaST client runlevel_auto 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/runlevel_auto.ycp:25 ---------------------------------------- 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] clients/runlevel_auto.ycp:26 Runlevel auto started 2013-03-06 05:33:48 <1> dhcp-172-16-170-244(3533) [YCP] RunlevelEd.ycp:52 Runlevel 4 support set to: false ########## It seems like maybe its unhappy about something related to the runlevel? My autoyast.xml has the following: ######### <configure> <runlevel> <default>3</default> </runlevel> ######### Is this no longer supported? The last version of the documentation seems to suggest that its still valid: http://users.suse.com/~ug/autoyast_doc/configuration.html#CreateProfile.Ser… As a side note, is autoyast still being actively maintained? All of the links on Uwe's website ( http://users.suse.com/~ug/ ) don't have any references to 12.3, and the OpenSUSE Yast Autoinstall wiki page is now gone ( http://en.opensuse.org/YaST_Autoinstallation ). -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

5 12

[opensuse-autoinstall] create initial profile causes iscsi termination?
by Per Jessen 12 Mar '13

12 Mar '13

I'm trying to create the initial autoyast profile, but the collection process seems to do something to iscsi (I have root on iscsi), which makes the systems hang. Unticking "iscsi initiator" makes the collection complete. -- Per Jessen, Zürich (10.1°C) http://www.dns24.ch/ - free DNS hosting, made in Switzerland. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 0

RE: [opensuse-autoinstall] RE: implement minimum hardware checking
by Hans-Joachim Ehlers 05 Feb '13

05 Feb '13

Sorry not but i think you are able to use the ask function of autoyast. http://doc.opensuse.org/projects/autoyast/configuration.html#CreateProfile.… See basically create a minimum install profile menationed in http://users.suse.com/~ug/AutoYaST_FAQ.html section: 1.4 What is smallest autoyast profile that makes sense? and combine that with the ask profile. Now you should have your minimum profile with a box that tells the user that the install faild because of ... and he can do nothing or reboot .... BTW: Why not using the rules.xml and a script within to tell the user that the installation failed ? hth Hajo -----Original Message----- From: Taluskie, Vincent [mailto:Vincent.Taluskie@emc.com] Sent: Thursday, January 17, 2013 8:16 PM To: Hans-Joachim Ehlers Subject: Re: [opensuse-autoinstall] RE: implement minimum hardware checking Thanks for your response, I will continue with the rules approach. The main profile I have now focuses on a successful install of my application. I need the simplest profile for failure that doesn't try to install any software - just abort with an error message. Is there an example of a simple failure profile you've seen? Vince On Jan 17, 2013, at 11:58 AM, Hans-Joachim Ehlers wrote: > -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] Some question about image installation feature
by Joschi Brauchle 03 Feb '13

03 Feb '13

Hello everyone, before I start doing some testing myself I wanted to ask the list if anyone has experience with image-based AutoYast installations? I see that openSUSE12.3 DVD brings some prebuilt images for Base,X11,KDE and so. See here: http://download.opensuse.org/repositories/openSUSE:/Factory/images/repo/ope… I have the following questions about image installation: 1) How would I include the prebuilt images from above? 2) What happens If I only need (let's say) about 90% of the packages installed in an image? Will the remaining 10% be uninstalled or stay? 3) What happens if updates are available for the packages contained in an image? Will YaST install updates additionally then? 4) If there is a YES to 3), does it make sense to use images in the long run? Usually, many components receive updates during a release lifetime, such that the benefit of image installation goes down over time, right? There is a problem with the TexLive installation being extremely slow in OS12.3 (https://bugzilla.novell.com/show_bug.cgi?id=801874) so I thought about creating an image for texlive to speed this up! Thanks for any help on the topic. I have not found good material in the AutoYast docs about this... - J Brauchle

1 0

[opensuse-autoinstall] Problem running systemd service script after autoyast installation
by Rainer Krienke 24 Jan '13

24 Jan '13

Hello, since opensuse 12.2 I use systemd instead of sysv-init. Most of the systems I install this way need a full integration in our local university network, which means the need of autofs as well as NIS and LDAP and more modifications to the system. Installation of such linux systems is based on an autoyast file I wrote. Part of this autoinstallation is a autoyast-post script that creates a systemd lfinalinstall.service file, that should start later on to do the network integration and all the rest. Before opensuse 12.2 this was done via a /etc/init.d/lfinalinstall init script that did just the same like the systemd lfinalinstall.service file does now. My problem is that I would like the service script to execute right after the autoyast installation of linux has finished (without a further reboot). So the autoyast installtion is done and the system comes up to the default runlevel starting kdm and now the service script should start. This used to work fine for the /etc/init.d script in earlier suse versions but does no longer work for 12.2 using systemd. The service file is activated but won't start. Only If I reboot the system after the complete autoyast installation one more time the script runs just fine, but not after the autoyast driven installation when it boots up to the default runlevel the first time, without one more reboot. The lfinalinstall.service file that is created by the autoyast post script (also tried chroot script) looks like below. After the .service file has been written I call /bin/systemctl enable lfinalinstall.service as well as a /bin/systemctl daemon-reload command. [Unit] Description=install script After=apparmor.service local-fs.target network.service Before= ConditionPathExists=/var/lib/lfinal/_run_install_ [Service] Type=oneshot Environment=SYSTEMD_NO_WRAP=1 TERM=linux ExecStart=/var/lib/lfinal/lfinalinstall # do network integration RemainAfterExit=yes TimeoutSec=0 ExecStartPost=/bin/rm -f /var/lib/lfinal/_run_install_ StandardInput=tty [Install] WantedBy=default.target The dependency file /var/lib/lfinal/_run_install_ is also in place. And of course the real script to do the job /var/lib/lfinal/lfinalinstall is also available and executable. After autoyast istallation has completed a "systemctl status lfinalinstall.service" shows this: $ systemctl status lfinalinstall.service lfinalinstall.service - lfinalinstall install script Loaded: loaded (/lib/systemd/system/lfinalinstall.service; enabled) Active: inactive (dead) CGroup: name=systemd:/system/lfinalinstall.servic Now I wonder why this script won't start after the installation has finished and the system boots up to the default runlevel? Does anyone have an idea or perhaps an idea how to debug this problem? The autoyast postinstall.log file shows that the lfinalinstall.service file has been created and enabled and that "systemctl daemon-reload" has been executed. Thanks Rainer -- Rainer Krienke, Uni Koblenz, Rechenzentrum, A22, Universitaetsstrasse 1 56070 Koblenz, http://userpages.uni-koblenz.de/~krienke, Tel: +49261287 1312 PGP: http://userpages.uni-koblenz.de/~krienke/mypgp.html,Fax: +49261287 1001312

2 2