February 2013 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] Failure with SuseConfig on Autoyast
by Mario Gzuk 13 Aug '13

13 Aug '13

Hi, since round about one week we get the following error. The setup stands in this state, autoinstall is broken. 2013-02-06 13:45:57 <1> hostname(7562) [YCP] clients/inst_autoconfigure.ycp:41 current step: 26 2013-02-06 13:45:57 <1> hostname(7562) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2013-02-06 13:45:57 <1> hostname(7562) [Interpreter] mail/widgets.ycp:121 Calling YaST client mail_auto 2013-02-06 13:45:57 <1> hostname(7562) [YCP] clients/mail_auto.ycp:31 ---------------------------------------- 2013-02-06 13:45:57 <1> hostname(7562) [YCP] clients/mail_auto.ycp:32 Mail auto started 2013-02-06 13:45:58 <1> hostname(7562) [YCP] SuSEFirewall.ycp:2522 Firewall configuration has been changed. Writing: $["FW_ALLOW_FW_BROADCAST_DMZ":"no", "FW_ALLOW_FW_BROADCAST_EXT":"no", "FW_ALLOW_FW_BROADCAST_INT":"no", "FW_CONFIGURATIONS_EXT":"sshd", "FW_DEV_EXT":"any eth0", "FW_IGNORE_FW_BROADCAST_DMZ":"no", "FW_IGNORE_FW_BROADCAST_EXT":"yes", "FW_IGNORE_FW_BROADCAST_INT":"no", "FW_IPSEC_TRUST":"no", "FW_LOAD_MODULES":"nf_conntrack_netbios_ns", "FW_LOG_ACCEPT_ALL":"no", "FW_LOG_ACCEPT_CRIT":"yes", "FW_LOG_DROP_ALL":"no", "FW_LOG_DROP_CRIT":"yes", "FW_MASQUERADE":"no", "FW_PROTECT_FROM_INT":"no", "FW_ROUTE":"no", "enable_firewall":false, "start_firewall":false]. 2013-02-06 13:45:58 <1> hostname(7562) [YCP] SuSEFirewall.ycp:2545 Disabling firewall services 2013-02-06 13:45:58 <1> hostname(7562) [YCP] Service.ycp:414 Disabling service SuSEfirewall2_setup 2013-02-06 13:45:58 <1> hostname(7562) [YCP] Service.ycp:414 Disabling service SuSEfirewall2_init 2013-02-06 13:45:58 <1> hostname(7562) [YCP] Service.ycp:403 Enabling service postfix 2013-02-06 13:45:58 <3> hostname(7562) [agent-ini] IniParser.cc(parse):556 Can not open /etc/sysconfig/amavis. 2013-02-06 13:45:58 <1> hostname(7562) [YCP] Service.ycp:82 Der Dienst amavis existiert nicht. 2013-02-06 13:45:58 <3> hostname(7562) [YCP] Service.ycp:165 Service amavis does not exist. 2013-02-06 13:45:58 <1> hostname(7562) [YCP] Service.ycp:82 Der Dienst freshclam existiert nicht. 2013-02-06 13:45:58 <3> hostname(7562) [YCP] Service.ycp:165 Service freshclam does not exist. 2013-02-06 13:45:58 <1> hostname(7562) [YCP] Service.ycp:82 Der Dienst clamd existiert nicht. 2013-02-06 13:45:58 <3> hostname(7562) [YCP] Service.ycp:165 Service clamd does not exist. 2013-02-06 13:45:58 <3> hostname(7562) [agent-ini] IniParser.cc(getTimeStamp):925 Unable to stat '/etc/sysconfig/amavis': Datei oder Verzeichnis nicht gefunden 2013-02-06 13:45:58 <3> hostname(7562) [bash] ShellCommand.cc(shellcommand):78 Setting up postfix local as MDA... 2013-02-06 13:45:58 <3> hostname(7562) [bash] ShellCommand.cc(shellcommand):78 Setting SPAM protection to "off"... 2013-02-06 13:46:00 <3> hostname(7562) [YCP] Report.ycp:523 Fehler bei der Ausführung von SuSEconfig. Can you help me with this issue? The file /etc/sysconfig/amavis exists at this state. Thank you. -- 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] 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] 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