openSUSE Autoinstall August 2013

autoinstall@lists.opensuse.org

15 participants
5 discussions

[opensuse-autoinstall] Add-on product URI naming scheme
by Andreas Taschner 30 Aug '13

30 Aug '13

Hi In an attempt to create SLES11SP2/3 installation images, which contain various repositories with some in-house developed RPMs, some questions have popped up from my customer. Although I have searched in the "usual places"++ (admit not being very good at that) I have not been able to find clear answers. > My question is how can I refer to a repository in an autoyast file, when > the repository resides in the same medium as the installation files? > > In my autoyast file I have > <add-on> > <add_on_products config:type="list"> > <listentry> > <media_url>cd:///repos/my_repo1</media_url> > <product>my_product1</product> > <product_dir>/</product_dir> > <name>my_product1</name> > </listentry> > </add_on_products> > </add-on> > > Should the media_url be cd:///<path> or can I use file:///<path>? > If I use a usb disk instead of a CD, should I change the cd:///<path> to > usb:///<path>? > Would it be possible to use relurl:///<path>? > In that case what is considered the root of the SuSE DVD installation > media, the root directory or some other path? > > It seems that cd:/// works for installation with a DVD. I didn't find > this in the documentation and I don't know if file:/// is supposed to > work or not. I once had a case about location of the info file for linuxrc (where one could refer to info=disk:/info?device=*usb*), but I am not sure this applies to AutoYaST. Also the paths available during installation are not clear to me. Is anybody willing to elaborate or point to sources that document the naming schemes and paths. Thank you. Best regards Andreas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

4 6

[opensuse-autoinstall] Creating encrypted passwords without yast ui
by Jochen Schaefer 29 Aug '13

29 Aug '13

Hi, I would like to achive the creation of the encrypted root password used within autoyast via cmdline. Could sombody tell me how to do that with python or perl or any os cmd-line tool? Thanks, Jochen

4 5

[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] install hangs inside of virtual machine
by Lonni J Friedman 08 Aug '13

08 Aug '13

Greetings, I'm trying to run an autoyast based installation of SLES11-SP3 inside of a KVM based virtual machine (host OS is Fedora19-x86_64, if that matters), and it is consistently hanging at: Sending dhcp request to eth0 It sounds quite similar to this bug: https://bugzilla.novell.com/show_bug.cgi?id=799496 however, I'm not installing over NFS at all. I'm invoking the installation from local media, and pulling down all components via http. This is the isolinux 'append' entry that I'm using: textmode=1 initrd=sles113_64bit.img autoyast=http://172.20.232.152/distros/suse/os/SLES11-SP3/x86_64/autoyastcuda.xml install=http://172.20.232.152/distros/suse/os/SLES11-SP3/x86_64 Has anyone else run into anything like this? thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

6 7

[opensuse-autoinstall] network devices changing ...
by Dr.Peer-Joachim Koch 01 Aug '13

01 Aug '13

Hi, on new DELL R820 I'm currently trying to install SLES11SP1. A newer version is not possible (software reasons ...). I used some older autoinstall file, which works for old nodes. On the new node the installations fails. 1) The initrd was modified (new tg3 and megariad_sas module. But both modules are not loaded automatically. I have to do this by hand. 2) When I start the installation process after loading the modules, everything seems to be fine, but after the first boot the network devices have changed. In in the udev rules file the eth{0,1} switched to eth{2,3} and eth{2,3} switched to eth{0,1}. So after the first boot, no network is available and I have to switch the udev rules (doing a rescue boot). Therefore not everything of the autoinstall script is executed. *) How can I check, why the modules are *not* loaded ? *) Can I force in the autoinstall file to create the udev rules according to the mac addresses (lowest mac adr. -> eth0; lowest mac adr.+1 ->eth1,...) -- Bye, Peer _________________________________________________________ Max-Planck-Institut fuer Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

2 2

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall August 2013