January 2013 - openSUSE Autoinstall - openSUSE Mailing Lists

[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

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] 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

[opensuse-autoinstall] keeping installed packages
by Erico Mendonça 17 Jan '13

17 Jan '13

Is there a variable in AutoYaST to make it keep the package cache on disk, like zypper does with "--download-only"? My idea was finding a way to make all packages used during installation available as a local repo in the hard disk as a makeshift "recovery" partition. So far I couldn't find a way other than copying the repos directly from the DVD... -- -- Erico -- 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] implement minimum hardware checking
by Taluskie, Vincent 17 Jan '13

17 Jan '13

Hi, I would like to implement minimum hardware checking for SUSE 11 (SP1) using autoyast installation. It looks like using AutoYast rules.xml file would be a good way to handle this: Ideally, if the hardware meets the requirements, then select the installation profile (passes_requirements.xml) and proceed as normal. One concept I am having a hard time finding docs around is how to flag failure during install. If there's not enough memory or disk to successfully support the application I am installing, I would like to return the fails_requirements.xml profile and show the user an abort message rather than doing the install. Does someone have a pointer to this kind of scenario? I have been searching but not finding much discussion around handling failure during the auto install. Thanks in Advance, vince -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2