- openSUSE Autoinstall

[opensuse-autoinstall] 13.1 problem on IBX-530
by 686f6c6d 22 Apr '14

22 Apr '14

Hello world, I'm experiencing a strange issue with 13.1s AutoYAST on IBX-530s [0]. Maybe some of you can help… We're using rules.xml to distinguish between a couple of machines, namely "real" servers, embedded devices (IBX) and more. The AutoYAST profiles for the real servers and the embedded devices have only trivial differences (re bootloader etc., nothing I'd suspect to have any relevance to the problem). The only other difference is that for real servers we use a static IP address (via hostip, nameserver, and gateway boot parameters), and for embedded devices we use DHCP. The real servers install and run just fine. With the embedded devices, stage 1 finishes just fine, AFAICT. After the reboot, stage 2 throws a few APCI errors (warnings?), then tells me systemd is about to flush the journal (we don't use a persistent journal), and then does nothing, YAST is never even displayed (textmode=1 on both servers and embedded). I have tried around 10 installs and waited for up to 90 minutes; my colleague who first experienced the problem said he waited for the journal for about five minutes and was then dropped to a non-functioning login prompt or shell, but I could not reproduce this. YAST is started seemingly started in the background according to the logs, and runs up to the first user prompt (we have to accept a GPG key because we manually-by-script add a custom add-on repo). Since I can't see YAST, I can't interact with it. I cannot find what is wrong, not even an error message; I am quite lost. I have attached some logs and command output. Can anybody shed some light on what is happening? I would really appreciate any kind of help, nudges in the right direction, or slaps in the back of the head to wake up my brain. (; [0]: http://www.ieiworld.com/search.aspx?keyword=ibx-530 -- Kind regards Christopher 'm4z' Holm / 686f6c6d "We must respect the other fellow's religion, but only in the sense and to the extent that we respect his theory that his wife is beautiful and his children smart." --H. L. Mencken

1 0

[opensuse-autoinstall] autoyast and partitions
by Dsant 15 Apr '14

15 Apr '14

If I use autoyast and xml file, without any partitions rules, will the existing partitions be safe ? That is, will I be asked about partition scheme ? Or will partitions be erased automatically ? -- : ` _..-=-=-=-.._.--. Dsant, from Lyon, France `-._ ___,..-'" -~~` __') forum(a)votreservice.com jgs `'"---'"`>>"'~~"~"~~>>'` =====================```========```======== -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 2

[opensuse-autoinstall] Installing with a Bonded Network broken when HW Clock is in the Future
by michael.leu＠mgb.ch 28 Mar '14

28 Mar '14

Hello Since about a year we always have to set the hardware clock on our physical servers to the correct time in GMT or else the AutoYaST install process would fail. Env: SLES 11 SP3 HW: HP ProLiant LAN: PXE boot on eth0 with dhcp, AutoYaST config with bond0 on eth0+eth1 As the root cause I believe it is ifprobe that thinks a change is only necessary if /etc/sysconfig/network/ifcfg-eth0 is newer than /dev/.sysconfig/network/ifup-eth0 Combined with this change it wreaks havoc to the bonded network at install time: rpm -qf /sbin/ifup --changelog [...] * Thu Apr 04 2013 mt(a)suse.de - Fixed to stop dhcp clients and remove IP addresses on not yet enslaved bridge ports and bonding slaves. The bridge or bond interface has the IP addresses assigned itself instead. The port/slave may still have IP addresses, when the IP config of an active (ethernet) interface has been moved into a bridge or bond config, e.g. while "virsh iface-bridge eth0 br0". There is no full ifdown for the port interface to not break the vlans (and their bridges) which may refer to the port too (bnc#813148). [0001-Flush-IPs-on-bridge-bond-children-ifup-bnc-813148.patch] [...] Now how does it come this far? Let me explain what I think happens: With the *old* ifup and a HW clock in the future: 1. eth0 with dhcp up 2. Yast configures eth0, eth1 and bond0 3. ifprobe compares it's runtime config of eth0 [0] with the ifcfg-eth0 in /etc/sysconfig (comparison with 'test -nt') and (wrongly) thinks nothing has changed 4. Yast does not take eth0 down because the ifprobe returncode indicates no action necessary 5. Yast ifups the bond0 and all slaves get deconfigured automaticall, including eth0 6. everything continues swimmingly With the *new* ifup and a HW clock in the future: 1. eth0 with dhcp up 2. Yast configures eth0, eth1 and bond0 3. ifprobe compares it's runtime config of eth0 [0] with the ifcfg-eth0 in /etc/sysconfig (comparison with 'test -nt') and (wrongly) thinks nothing has changed 4. Yast does not take eth0 down because the ifprobe returncode indicates no action necessary 5. Yast ifups the bond0 but all slaves get left as-is, including eth0 with it's DHCP IP and route 6. Network does not work, repo does not get found, installation aborts With the *new* ifup and a HW clock set correctly or in the past: 1. eth0 with dhcp up 2. Yast configures eth0, eth1 and bond0 3. ifprobe compares it's runtime config of eth0 [0] with the ifcfg-eth0 in /etc/sysconfig (comparison with 'test -nt') and notices the config has changed 4. Yast sees the returncode of ifprobe and takes eth0 down 5. Yast ifups the bond0 but all slaves get left as-is, including eth0 which is now in the correct state 6. everything continues swimmingly I've come to this conclusion by reading /var/log/messages and looking at the two files ifprobe compares. This is how it looks when the server time is slightly in the future: / # ls -al /dev/.sysconfig/network/ifup-eth0 /etc/sysconfig/network/ifcfg-eth0 -rw-r--r-- 1 root root 7 Mar 11 20:56 /dev/.sysconfig/network/ifup-eth0 -rw-r--r-- 1 root root 73 Mar 11 20:55 /etc/sysconfig/network/ifcfg-eth0 Note the runtime config is one minute in the future, this leads to ifprobe thinking there is no change necessary. What do you think? Is this a reasonable explanation? I'll open a case for SLES but maybe this also affects OpenSUSE. Regards, Michael Leu [0] /dev/.sysconfig/network/ifup-eth0 -- 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] Systemd Networkdevices
by Sebastian Gödecke 26 Mar '14

26 Mar '14

Hi, is it possible to use variables für the devices section in autoyast to handle one script for nearly all networkdevices ? I often use enp0s3 but now on an older laptop it is enp2s0. Is there an argument for many devices ? -- Mit freundlichen Grüßen Sebastian Gödecke -- 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] loginmanager lightdm
by Sebastian Gödecke 26 Mar '14

26 Mar '14

Hi ML, i want to use an other loginmanager for my configuration, something like LightDM for XFCE. What are the changes i need to do to habe lightdm as loginmanager ? this here is a part of my xml: <packages config:type="list"> <package>gdm</package> <package>nss_ldap</package> <package>oss-client-control-daemon</package> <package>pam_ldap</package> <package>quota-nfs</package> <package>xlockmore</package> </packages> <patterns config:type="list"> <pattern>base</pattern> <pattern>fonts</pattern> <pattern>games</pattern> <pattern>imaging</pattern> <pattern>non_oss</pattern> <pattern>sw_management</pattern> <pattern>x11</pattern> <pattern>xfce</pattern> <pattern>xgl</pattern> <pattern>yast2_basis</pattern> <pattern>yast2_install_wf</pattern> </patterns> </software> <sysconfig config:type="list"> <sysconfig_entry> <sysconfig_key>RUN_PARALLEL</sysconfig_key> <sysconfig_path>/etc/sysconfig/boot</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>DEFAULT_WM</sysconfig_key> <sysconfig_path>/etc/sysconfig/windowmanager</sysconfig_path> <sysconfig_value>xfce</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>INSTALL_DESKTOP_EXTENSIONS</sysconfig_key> <sysconfig_path>/etc/sysconfig/windowmanager</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>gdm</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>DISPLAYMANAGER_SHUTDOWN</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>all</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>KDM_GREETSTRING</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>Open School Server Client</sysconfig_value> </sysconfig_entry> <sysconfig_entry> <sysconfig_key>KDM_USERS</sysconfig_key> <sysconfig_path>/etc/sysconfig/displaymanager</sysconfig_path> <sysconfig_value>no</sysconfig_value> </sysconfig_entry> </sysconfig> Regards Sebastian -- Mit freundlichen Grüßen Sebastian Gödecke -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 2

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

[opensuse-autoinstall] Network interface configuration and systemd's predictable network interface names
by David Huffman 28 Jan '14

28 Jan '14

Hi, thanks to systemd's predictable network interface names (http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfac…) I have no way to tell what my eth0 interface is actually going to be called ahead of time as it varies amongst different computers. Is there anyway to affect all available network interfaces with autoyast? <networking> <interfaces config:type="list"> <interface> <bootproto>dhcp</bootproto> <device>How do I make it affect all devices? Or at least systemd's equivalent to eth0.</device> <startmode>onboot</startmode> </interface> </interfaces> </networking> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

5 4