February 2014 - openSUSE Autoinstall - openSUSE Mailing Lists

[opensuse-autoinstall] State of Autoyast for OpenSUSE 13.1
by Joschi Brauchle 18 Dec '14

18 Dec '14

Hi everyone, sorry for asking such a general question, but what is the state of AutoYast for OpenSUSE 13.1? I converted a completely working XML from a 12.3 installation to 13.1. The autoinstallation finishes, but the installed system is - missing Sysconfig configuration from <sysconfig> section - has not run any of the <post-scripts> and <init-scripts> - does not accept the root password configured in the <users> section - is missing all files installed from the <files> section of the XML - misses LDAP and KRB config from <ldap> and <kerberos> - services are not configured as in <services> and many more problems. To me it looks like the complete second stage is missing, as all those things are done there. Is this a known problem? Or are there known problems for 13.1? Did anyone succeed with AutoYast and 13.1 with any of the above mentioned XML sections? The y2log file from second stage is very small and does not show any errors... Best regards, Joschi Brauchle

6 25

AW: Antwort: [opensuse-autoinstall] LVM Installation fails
by ralf.prengel＠comline.de 25 Feb '14

25 Feb '14

>Von: Oliver.van.der.Velde(a)Edeka.de [mailto:Oliver.van.der.Velde@Edeka.de] >Gesendet: Montag, 24. Februar 2014 16:36 >An: Prengel, Ralf >Cc: opensuse-autoinstall(a)opensuse.org >Betreff: Antwort: [opensuse-autoinstall] LVM Installation fails >hi, >we experienced serveral problems letting autoyast wiping old partition tables . you cant be sure that all tables are wiped completely. >so we decided to erase all data manually using dd before starting installation. you can automate this inside a pre script . >this is what the docu tells us . >(..) > <drive> ><device>/dev/sdb</device> ><initialize config:type="boolean">true</initialize> >(..) >we are using sles10.4 sles11.2 sles11.3 and the problems are still there. Hallo, thanks fort he answer. Could you post the config for a postscript. I m a beginner using autoyast. Thanks Ralf Ralf Prengel Manager Customer Care Comline AG Hauert 8 D-44227 Dortmund/Germany T +49 231 97575 904 F +49 231 97575 257 M +49 151 10831 157 E ralf.prengel(a)comline.de www.comline.de Vorstand Stephan Schilling Aufsichtsrat Otto Prange (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422 -- 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] LVM Installation fails
by ralf.prengel＠comline.de 24 Feb '14

24 Feb '14

Hallo, I m preparing Suse autoyast installations for all versions opensuse 11.1 to 12.. My problem: Partitioning doesn t work if a lvm configuration is used. Has anyone working examples for a setup that - deletes existing partions - is working with all versions Thanks Ralf Ralf Prengel Manager Customer Care Comline AG Hauert 8 D-44227 Dortmund/Germany T +49 231 97575 904 F +49 231 97575 257 M +49 151 10831 157 E ralf.prengel(a)comline.de www.comline.de Vorstand Stephan Schilling Aufsichtsrat Otto Prange (Vorsitzender) HR Dortmund B 14570 USt.-ID-Nr. DE 124727422 -- 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] cobbler and autoyast rules.xml
by Michal Šebeň 21 Feb '14

21 Feb '14

Hello mates, looks like cobbler's kickstart template mechanism isn't ready for autoyast rules.xml feature: http://doc.opensuse.org/projects/autoyast/rulesandclass.html ( and I don't want to use pre-install scripts for autoyast.xml replace ) I think one possible solution is limit location (in this cobbler case) of profile files only to "rules" dir (same as rules.xml), this step will setup form["rules"] variable with "rules.xml" or requested profile name see: https://github.com/cobbler/cobbler/blob/master/bin/services.py, which can be later used for setup template name for generating autoyast/rules file - of course it requires some code on cobbler side any thoughts about this location restriction or other proposal ? thanks -- 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] Network interface configuration and systemd's predictable network interface names
by 686f6c6d 17 Feb '14

17 Feb '14

Damn you, gmail android app. Again for the list. ---------- Forwarded message ---------- From: Christopher 'm4z' Holm […] Date: Thu, Feb 6, 2014 at 9:29 AM Subject: Re: [opensuse-autoinstall] Network interface configuration and systemd's predictable network interface names To: Joschi Brauchle <joschi.brauchle(a)tum.de> Cc: opensuse-autoinstall(a)opensuse.org On Jan 28, 2014 6:52 PM, "Joschi Brauchle" <joschi.brauchle(a)tum.de> wrote: > > Hi, I am having the same problem. > > Could anyone post an XML snipped on how to provide these options to the kernel for the installation system and with autoyast to the installed system? (Mobile right now, all from the top of my head.) For the installation, you need to get the boot parameters ("biosdevname=0 net.ifnames=0") on the kernel commandline (either manually or by baking a custom image) or use the alternative ways for each (which I don't know by heart, IIRC for PNIN you have to remove or create some udev file, should be explained in the URL of my earlier message; CNDN was somewhat similar IIRC). For the installed system, if you choose to use the boot parameters, you need to get them into grub.cfg: - in 13.1 by patching /etc/default/grub for future kernels and /boot/grub2(?)/grub.cfg for the current kernel, or run "grub2-mkconfig -o /boot/grub2(?)/grub.cfg"[0] for the latter after you've patched /etc/default/grub; - for 12.3 I don't remember if the former or the following instructions will work; - for previous oS releases use /etc/sysconfig/bootloader instead of /etc/default/grub). 0: Although this alternative might not work; I haven't yet figured out how exactly GRUB config creation works, IIRC /etc/default/grub or /etc/sysconfig/bootloader contains a comment to the effect of something like "If there are custom parameters in grub.cfg, they will be taken from there (or merged with those in /etc/default/grub), else they will be taken from /etc/default/grub." For the custom image for stage1 I can give you a crude script. For the installed system (stage 2 and later), I'm still working on the 13.1 (and maybe 12.3, too) variant. -- I'm unsure whether this is what you asked for, but nobody else answered. (; Christopher 'm4z' Holm / 686f6c6d "Faith is what you have in things that don't exist." --Homer Simpson -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

1 1