openSUSE Autoinstall March 2014

autoinstall@lists.opensuse.org

3 participants
4 discussions

[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

[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

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall March 2014