openSUSE Autoinstall May 2012

autoinstall@lists.opensuse.org

6 participants
10 discussions

by John Willis

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

8 years, 11 months

[opensuse-autoinstall] autoyast with multiple LVM Volume Groups

by big beer

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

9 years, 2 months

[opensuse-autoinstall] update repo/kernel-default problems [was: 12.1, autoyast and systemd]

by 686f6c6d

Splitting this because AFAICT it has nothing to do with systemd, I just ran into it while trying to get systemd to work. On Tue, Apr 10, 2012 at 1:19 PM, 686f6c6d <686f6c6d(a)googlemail.com> wrote: > On Mon, Apr 2, 2012 at 16:16, 686f6c6d <686f6c6d(a)googlemail.com> wrote: >> >> - Using kernel-default-3.1.0-1.2.1.x86_64 from the "install" repo, the >> installation succeeds. >> - Using kernel-default-3.1.9-1.4.1.x86_64 from the "update" repo, the >> installation fails. > > Let me correct that: Once I changed the profile again to re-include > some of our scripts (that were disabled while debugging), even > kernel-default 3.1.0 fails with the same problem. > Need to do further debugging. Those seem to be unrelated problems. One thing I can say with certainty right now is that my profile does not work when I enable the update repo: installation of kernel-default fails because large parts of the device nodes in /dev are missing. When I disable the repo, everything works fine. Uwe: What is the best way to proceed from here? Should I open a bug for autoyast (although autoyast is not the real culprit here), or should we debug further on this list/off-list and then open bugs for the correct packages? I'm currently sanitizing the logs of both installations with and without the update repo enabled, which will take a while. -- Kind regards 686f6c6d / Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 3 months

[opensuse-autoinstall] Installation: Can't configure net with "linuxrc"

by Dominik Baumann

Hello, for using autoyast per http i want to configure network with linuxrc [1] and its kernel boot parameters (hostip, netmask, ...), resp. with the appropriate installation dialogue [2]. Unfortunately both don't work for me: The machine doesn't react to ping nor is "ifconfig -a" showing an active network interface or ip address. But i can set it manually with "ifconfig eth0 inet ..." at the same phase of installation, so missing network drivers shouldn't be the problem. The problem appears both on opensuse release 12.1 and 12.2/Milestone-3, both in a virtual and a physical machine. Any hints? PS: I know that linuxrc hasn't directly to do with autoyast, but perhaps it's often used there(?). I already asked at the german opensuse-de@ mailing list, but found no solution there. Dominik. [1] http://en.opensuse.org/SDB:Linuxrc [2] http://paste.opensuse.org/6379e182 http://paste.opensuse.org/af7f337d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 4 months

[opensuse-autoinstall] 12.1, autoyast and systemd

by 686f6c6d

Hi, here's the problems I ran into. They all seem to be related to systemd, but I did not want to hijack the other thread, although this one might solve the other problem, too. 1. The final kexec/reboot is not executed. Both <final_reboot config:type="boolean">false</final_reboot>, meaning kexec will be used, and <final_reboot config:type="boolean">true</final_reboot> have no effect at all[0]. This also means that... 2. Init-Services (<runlevel>) defined in autoyast are not started/stopped, so, f.e., no ssh keys are generated. (This also results in a lot of subsequent errors in our setup.) To fix this, just include: <software> <remove-packages config:type="list"> <package>systemd-sysvinit</package> </remove-packages> </software> This way, sysvinit-init will be installed and used. When can we expect autoyast to support systemd? [0]: Once you do a manual reboot (if you happen to have access other than ssh to the machine), the machine will do the autoyast kexec/reboot after that. -- Kind regards/Mit freundlichen Grüßen Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 4 months

[opensuse-autoinstall] ldap-configuration using ldap

by Robert Klein

Hi, I'm currently testing ldap-client configuration using autoyast. Here is a list of issues I found. Please comment. I'll probably file some bug reports next week. Testing system is factory snapshot from April 12, 2012 (that is, M3, probably). - (YaST) Issues during installation: - Both the reference profile and the XML schema allow the parameter <bind_dn>, but there's no binddn in /etc/ldap after installation. - missing support for additional LDAP configuration parameters, for example there ought to be a parameter <bind_pw> resulting in a bindpw in /etc/ldap.conf after installation. Also, I could use a way wo put the tls certfile into the autoyast xml, e.g. using a parameter <tls_cacertfile-content><source><![CDATA[...]]></... - Yast Reference Profile (created using Yast -> Autoyast -> Tools -> Create Reference Profile) issues: - A created reference profile has a parameter <mkhomedir>, but it isn't allowed according to the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) and apparently isn't used, i.e. it didn't appear in /etc/ldap.conf after installation (I only had it set to "false", though). - schema only issues: - The parameters <sssd>, <tls_cacertdir> and <tls_cacertfile> aren't in the XML schema (/usr/share/YaST2/schema/autoyast/rng/ldap.rng) They are, however reference profiles created with Yast -> AutoYast and are used during installation Thanks and best regards Robert -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 4 months

[opensuse-autoinstall] YaST (incl. AutoYaST) is on github now

by Uwe Gansert

Hi, thanks to all the people from the team who made that move possible! https://github.com/yast/yast-autoinstallation I'm waiting for your pull requests now ;) ciao, Uwe Gansert SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 6 months

Antw: Re: [opensuse-autoinstall] problem installing from dhcp an two netcards

by Jochen Schaefer

Hi Christopher, thanks for your reply. I'm using SLE11-SP1 and keep_install_network. We also use the xml syntax to achieve persistent names. But that is not related to this point in time when the error occurs. I try to describe the configuration in detail: boot via PXE/DHCP transtec desktop/server with 2 nics, one nic not connected. For an unknown reason installation takes place via eth1 even if I change the cable to the other nic. When booting into stage 2 the device naming automatically changes. eth1 becomes eth0 and vice versa We have a udev rule in autoinst.xml which persists one mac to eth0 because we need eth0 as bridge port. The file /etc/sysconfig/network/ifcfg-eth0 is missing since eth1 has been used in stage 1. Yast initializes network interfaces in stage 2, does not find any configuration for eth0 and will not initialize eth0 which now is the active card. eth1 (previously eth0) is now the interface which has no connection to the network source but a valid interface description. I solved the problem by creating /etc/sysconfig/network/ifcfg-eth0 via a chroot (chrooted=true) script. We just need to tell Yast executing dhcp at this interface. Something like "BOOTPROTO='dhcp4', STARTMODE="onboot" and NAME='XYZ' is sufficient since autoyast will change the network configuration within the LAN part anyway. But nevertheless I don't understand why the interface change always happens. And I would like to resign the workarround. Best Regards, Jochen >>> 686f6c6d <686f6c6d(a)googlemail.com> schrieb am 5/17/2012 um 1.34 Uhr in Nachricht <CAMEHyeHR-k+m7FfGfxsaSgn=ccfZwui75HXVHbd9F=mX-MndCQ(a)mail.gmail.com>: > Which oS/SL release do you use? > Do you use keep_install_network? > > Does the SLE11 fix (Q1.10) work for you? > http://turing.suse.de/~ug/AutoYaST_FAQ.html#a9 > > (@Uwe: The link in Q1.12 is dead.) > > Is/are the card/s bnx2? (There's a bug in SL10 SP2 IIRC.) > > -- > Mit freundlichen Grüßen > Christopher 'm4z' Holm > Am 14.05.2012 19:11 schrieb "Jochen Schaefer" <jschaef(a)novell.com>: > >> Hi list, >> >> I have a problem when installing a machine via pxe with two network cards. >> Doesn't matter if both cards are connected or the first or the second card >> the naming of the devices >> always changes. >> >> eth0 in stage 1 becomes eth1 in stage two (before static network >> configuration takes place) and vice versa. >> When the machine is comming up into stage two it claims that no >> configuration is found for eth1 and tries to >> connect via the other interface but that one is not connected to the >> installation source. >> >> If changing the cables than the process is going vice versa. In stage one >> network source will be accessed >> via eth1 which becomes eth0 in second stage. But no configuration found >> for eth0. >> >> Is there anything known about that behaviour. Can I workarround that? >> >> I already tried with netdevice parameter but that didn't help. >> >> >> Thanks, >> Jochen >> >> -- >> To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org >> To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org >> >> -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 6 months

Re: [opensuse-autoinstall] problem installing from dhcp an two netcards

by 686f6c6d

Sorry, again for the list. My "smart"phone did things the list did not like (multipart and/or HTML) and it was rejected. On Thu, May 17, 2012 at 1:34 AM, 686f6c6d <686f6c6d(a)googlemail.com> wrote: > Which oS/SL release do you use? > Do you use keep_install_network? > > Does the SLE11 fix (Q1.10) work for you? > http://turing.suse.de/~ug/AutoYaST_FAQ.html#a9 > > (@Uwe: The link in Q1.12 is dead.) > > Is/are the card/s bnx2? (There's a bug in SL10 SP2 IIRC.) > > -- > Mit freundlichen Grüßen > Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

9 years, 6 months

[opensuse-autoinstall] autoyast pxe + proxy = error

by Dr.Peer-Joachim Koch

Hi, I want to upgrade a couple of HPC nodes. All working in a private subnet. To get access to some additional repositories I need a proxy config. But when I add the proxy and proxyport statement at the pxe server for the (test) node, the autoyast file is not found. Without the proxy statements the autoyast file is found, but many packages are not found ;( I've tested the proxy using wget and everything is working from the cli. Any idea what's wrong or howto debug ? LABEL install KERNEL kernel APPEND initrd=initrd showopts install=nfs://192.168.1.100/Net/Groups/Services/LNX_FTP/INSTALL/sles11SP1/x86_64/ autoyast=http://192.168.1.100/sysinst/autoyast/node25 textmode=1 netdevice=eth0 dhcp=1 proxy=192.168.1.100 proxyport=3128 -> no autoyast found APPEND initrd=initrd showopts install=nfs://192.168.1.100/Net/Groups/Services/LNX_FTP/INSTALL/sles11SP1/x86_64/ autoyast=http://192.168.1.100/sysinst/autoyast/node25 textmode=1 netdevice=eth0 dhcp=1 -> autoyast found, no external sources ... -- Thanks and 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

9 years, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall May 2012