- openSUSE Autoinstall

[opensuse-autoinstall] Subtle differences between 42.x(?) DVD- and NET-ISOs with AutoYAST
by 686f6c6d 16 Aug '17

16 Aug '17

Greetings, we're experiencing the following strange issue: We (re-)install our laptops using a USB boot stick and AutoYAST profiles on an HTTP server. Since openSUSE 11.x, we've used the openSUSE-*-DVD-type ISOs for this: - Put the image on the stick (with dd), - boot, enter "autoyast=http://foo/bar", - laptop gets IP and DNS via DHCP, - AutoYAST fetches the profile for the MAC of the laptop and installs… great! For some reason, with openSUSE Leap 42.3 and 42.2 (haven't tested more, but my documentation indicates it worked with 42.1), there's a problem with the DVD-flavour ISOs. If we use these on our boot stick, then during bootup eth0 won't be brought up, won't get IP and DNS info and hence AutoYAST is unable to fetch the profile and install successfully. (Variant: When we don't enter our HTTP source as boot parameter but via the bootloader menu entry "Source (F4)", eth0 does successfully come up during startup and fetches IP and DNS info via DHCP, but then fails in a different way: For some reason, AutoYAST then still wants to configure wlan0 on the laptop as well and fails to find the AutoYAST profile if no wireless connection data is entered or available.) We've tried creating the boot media with both plain "dd" and the (openSUSE RPM) "imagewriter" with identical results. Once we use the NET-flavour ISOs for our boot stick, it works as expected. Is this expected behaviour? Is it a known issue? -- 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 -- 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] 2 questions about VLAN and autoinstall
by Dr. Peer-Joachim Koch 11 Aug '17

11 Aug '17

Hi, following questions: 1) Is it possible to use tagged vlans for installation ? If yes, how do I tell the system with vlan tag to use ? 2) Does anybody know how to set up tagged vlans with a Intel X710 (i40e module) ? I tried it the old way (ifcfg-vlanID ...), but this is not working. I did not found any example .. Do I have to use the VF (virtual functions) ? -- Bye, Peer ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

1 0

[opensuse-autoinstall] examples files with rules or classes
by Fabien Chaudier 05 Jul '17

05 Jul '17

Hello, I have a big autoinst.xml and I don't know where to start. Some configuration files would be a good start for me. Thank you in advance -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 4

[opensuse-autoinstall] How to configure /etc/nsswitch.conf
by Dr. Peer-Joachim Koch 07 Jun '17

07 Jun '17

Hi, I want to change settings in the /etc/nsswitch.conf Currently it contains "files ldap" and we need "files sss" , but I did not find where to configure this item ... Any idea ? -- Bye, Peer ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

1 0

[opensuse-autoinstall] Mountpoint not created
by Dr. Peer-Joachim Koch 24 May '17

24 May '17

Hi, I want to create a "/scratch" folder within the autoyast setup. But the installation stops showing an error -3003 (mount point does not exist...) Where do I have to define/create the mount point ? ... <partition> <create config:type="boolean">true</create> <crypt_fs config:type="boolean">false</crypt_fs> <filesystem config:type="symbol">ext4</filesystem> <filesystem_id config:type="integer">131</filesystem_id> <format config:type="boolean">true</format> <loop_fs config:type="boolean">false</loop_fs> <mount>/scratch</mount> <mountby config:type="symbol">device</mountby> <partition_id config:type="integer">131</partition_id> <partition_nr config:type="integer">2</partition_nr> <resize config:type="boolean">false</resize> <size>30G</size> <stripes config:type="integer">1</stripes> <stripesize config:type="integer">4</stripesize> </partition> ... -- Bye, Peer ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

2 3

[opensuse-autoinstall] partion problem
by Peer-Joachim Koch 02 Mar '17

02 Mar '17

Hi, I'm currently updating 5 identical computer. The autoyast files are identical (only different hostname and ip). However the last machine will not install. The problem is: The two disks are not /dev/sda and /dev/sdb, but /dev/sdb and /dev/sdc. So the autoyast file does not fit .... When I look at the shell I do not see any /dev/sda. Any idea, why the devices are mapped wrong ? Bye, Peer -- _________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

2 1

[opensuse-autoinstall] Adding update for kernel module
by Dr. Peer-Joachim Koch 23 Feb '17

23 Feb '17

Hi, I've to install SLES11SP3 on some newer DELL hardware (R730, R330). Problem: the module for the perc controller is to old, so the system won't see a, hard disk. I patched the initrd with a newer kernel module - installation works fine. The problem is now the installed kernel-rpm does not contain the new driver and the system will not boot. So what is the best way to add this additional rpm before the system is booting the first time, but after installing the kernel ? -- Bye, Peer ________________________________________________________ Max-Planck-Institut für Biogeochemie Dr. Peer-Joachim Koch Hans-Knöll Str.10 Telefon: ++49 3641 57-6705 D-07745 Jena Telefax: ++49 3641 57-7705

1 1

Re: [opensuse-autoinstall] autoyast installation in Xen DomUs -- defining /etc/fstab ?
by lssl＠ssl-mail.com 14 Feb '17

14 Feb '17

Hi On Tue, Feb 14, 2017, at 05:19 AM, Erico Mendonça wrote: > Remember, in AutoYaST, less is more. 'less' is good. Trying to get to the most straightfwd way to build, configure & deploy Xen guests withOUT excess. For Opensuse at least pretty sure AY is part of the equation. > Where in that case would I set the 'proc', 'sysfs', debugfs', & 'devpts' > > mounts? They're not *additional* partitions, and from the docs, for a > > given partition I can only have one <mount>...</mount>. > > <snip> > > You shouldn't need it. IIRC, AutoYaST already adds these by default. It adds them by default, but what if I change the default fstopts for those mounts, e.g.? Or add an additional mount? Atm, adding changes to the Guest's /etc/fstab, then creating/examining a reference profile show no trace of my change. E.g., after adding /home/test/JUNK /mnt/JUNK none bind 0 0 to /etc/fstab, and re-creating a all-selected reference profile, I see no mention of the mount in the autoyast profile output. Unclear whether I've missed something in the profile generation, or it's simply not dealt with. > The easiest way would be to install the package yast2-autoyast on a machine > that already has these entries defined in /etc/fstab. Then run "yast2 > autoyast", select "Hardware", "Partitioning", then hit "Clone". > > You should be able to edit and export a valid XML. Kindof cheating, rather than rtfm'in up-front, by hey -- it works! Once I figure out the fstab bits ... -- 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] autoyast installation in Xen DomUs -- defining /etc/fstab ?
by lssl＠ssl-mail.com 14 Feb '17

14 Feb '17

I'm setting up autoyast for autoinstall of Xen DomUs. Both Xen Host & Guests run Opensuse Leap 42.2. >From my Dom0 I pass pre-formatted, but not yet populated, LVMs as disks to the DomU config guest.cfg ... disk = [ 'phy:/dev/VG0/EFI,xvda,w','phy:/dev/VG0/ROOT,xvde,w'] ... I want my Guest /etc/fstab to end up as UUID=AAAA-BBBB /boot/efi vfat [ ... efi fstab options ... ] 0 2 UUID=111...111 / ext4 [ ... root fstab options ... ] 1 1 proc /proc proc defaults 0 0 sysfs /sys sysfs noauto 0 0 debugfs /sys/kernel/debug debugfs noauto 0 0 devpts /dev/pts devpts mode=0620,gid=5 0 0 My question is how 'best' to set the 'proc', 'sysfs', debugfs', 'devpts' mounts & their respective fstopts? In the autoyast.xml that'll get passed to the xen.cfg, IIUC, I can use <partitioning> for the passed-in devices, with 'initialize', 'create' & 'format' all == "false", <partitioning config:type="list"> <drive> <device>/dev/xvda</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean" >false</create> <format config:type="boolean">false</format> <mount>/boot/efi</mount> <mountby config:type="symbol">uuid</mountby> <fstopt>[ ... efi fstab options ... ]</fstopt> <size>max</size> <filesystem config:type="symbol">vfat</filesystem> <partition_nr config:type="integer">1</partition_nr> </partition> </partitions> </drive> <drive> <device>/dev/xvde</device> <initialize config:type="boolean">false</initialize> <partitions config:type="list"> <partition> <create config:type="boolean" >false</create> <format config:type="boolean">false</format> <mount>/</mount> <mountby config:type="symbol">uuid</mountby> <fstopt>[ ... root fstab options ... ]</fstopt> <size>max</size> <filesystem config:type="symbol">ext4</filesystem> <partition_nr config:type="integer">1</partition_nr> </partition> </partitions> </drive> </partitioning> Where in that case would I set the 'proc', 'sysfs', debugfs', & 'devpts' mounts? They're not *additional* partitions, and from the docs, for a given partition I can only have one <mount>...</mount>. One option would be to use a postpartitioning script <scripts> <postpartitioning-scripts config:type="list"> <script> cat EOF >> /etc/fstab ( ... fstab entries for 'proc', 'sysfs', debugfs', & 'devpts' ... ) EOF </script> </postpartitioning-scripts> </scripts> , modifying the just-created-fstab immediately after the <partitioning> step. That's doable, but seems messy. What's the recommended way to get to a completely defined fstab in the Xen-DomU-install case above? -- 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] ssh_host-keys are preserved by autoinstallation despite formating the disk
by m.frerichs 06 Dec '16

06 Dec '16

Hello, I find out a special behaviour of autoyast under LEAP 42.1 concerning ssh-keys. It seems that ssh-keys in /etc/ssh are preserved from the old existing system, even if I recreate and reformat the disk . Is it true that such a feature exists and why? Are there other configurations which are preserved? Our constallation of several workstations is : Leap 42.1 Kernel : 4.1.34-33-default This misfunction got apparent , when we exchanged the disks of two clients because of different needed disp space for the two users . After a complete new installation by autoyast we reached that client 1 got the ssh-keys of client 2 in /etc/ssh and vice versa. I debugged it and i see the inverted files in chroot-scripts.log even before my post.sh -Script was mounted from Installserver and executed. I do not explicitly generate ssh-keys in my post.sh. After installation has completed , there is a new ssh_host_ed25519_key added . So i think it is not my mistake. zam221:/var/adm/autoinstall/logs # cat chroot-scripts.log + ls -lsai /etc/ssh total 292 523490 4 drwxr-xr-x 2 root root 4096 Nov 30 12:11 . 523265 12 drwxr-xr-x 146 root root 12288 Nov 30 12:14 .. 523471 4 -rw-r--r-- 1 root root 2375 Sep 9 16:10 ldap.conf 523720 228 -rw------- 1 root root 231821 Sep 9 16:10 moduli 524087 4 -rw-r--r-- 1 root root 2996 Sep 9 16:10 ssh_config 524085 8 -rw-r----- 1 root root 4530 Sep 9 16:10 sshd_config 541861 4 -rw------- 1 root root 668 Jul 26 14:25 ssh_host_dsa_key 541862 4 -rw-r--r-- 1 root root 602 Jul 26 14:25 ssh_host_dsa_key.pub 541865 4 -rw------- 1 root root 227 Jul 26 14:25 ssh_host_ecdsa_key 541866 4 -rw-r--r-- 1 root root 174 Jul 26 14:25 ssh_host_ecdsa_key.pub 541859 4 -rw------- 1 root root 977 Jul 26 14:25 ssh_host_key 541860 4 -rw-r--r-- 1 root root 642 Jul 26 14:25 ssh_host_key.pub 541863 4 -rw------- 1 root root 1675 Jul 26 14:25 ssh_host_rsa_key 541864 4 -rw-r--r-- 1 root root 394 Jul 26 14:25 ssh_host_rsa_key.pub + cat /etc/ssh/ssh_host_rsa_key.pub ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCwGkPV58BpMCK2/M3jsIjEy9UD7g/J2BAOBqMj6v3 g6E/w4YQ+1zmS1OKt9hILDOEK7V1vYgybaPSgQ20JzTyJo0rlw2bpnPp7zMTmYEBblkDAvJbWrsQ64hrR 5DNy1Wv8sxVGkVOyx+rGSXgRABsNstQJCz945ysITBKcexLK+aEIAY7PvOdQdHnOFwzABSUNdZXjQrMeFN6b KtloPPbnma+zUOyWPmBIbcqfzobgG6bUeF0tvjRVLyWh7cNTimsMZQKIoNNWcxLG8sS7fWWErTvvnGa+SHItTf e1HoCWJWN+yuw9vqre0xl6hkxwiEIlLpe772FxFvPuQDu9VePN root@zam1188 After Installation: zam221: ls -lsai /etc/ssh total 312 523490 4 drwxr-xr-x 2 root root 4096 Nov 30 12:14 . 523265 12 drwxr-xr-x 177 root root 12288 Dec 1 07:20 .. 523471 4 -rw-r--r-- 1 root root 2375 Sep 9 16:10 ldap.conf 523720 228 -rw------- 1 root root 231821 Sep 9 16:10 moduli 524087 4 -rw-r--r-- 1 root root 3630 Apr 14 2014 ssh_config 541907 4 -rw-r--r-- 1 root root 2996 Sep 9 16:10 ssh_config.install 541861 4 -rw------- 1 root root 668 Jul 26 14:25 ssh_host_dsa_key 541862 4 -rw-r--r-- 1 root root 602 Jul 26 14:25 ssh_host_dsa_key.pub 541865 4 -rw------- 1 root root 227 Jul 26 14:25 ssh_host_ecdsa_key 541866 4 -rw-r--r-- 1 root root 174 Jul 26 14:25 ssh_host_ecdsa_key.pub 541923 4 -rw------- 1 root root 399 Nov 30 12:14 ssh_host_ed25519_key 541924 4 -rw-r--r-- 1 root root 93 Nov 30 12:14 ssh_host_ed25519_key.pub 541859 4 -rw------- 1 root root 977 Jul 26 14:25 ssh_host_key 541860 4 -rw-r--r-- 1 root root 642 Jul 26 14:25 ssh_host_key.pub 541863 4 -rw------- 1 root root 1675 Jul 26 14:25 ssh_host_rsa_key 541864 4 -rw-r--r-- 1 root root 394 Jul 26 14:25 ssh_host_rsa_key.pub 541926 0 lrwxrwxrwx 1 root root 20 Nov 30 12:14 ssh_known_hosts -> /etc/ssh_known_hosts 524085 8 -rw-r----- 1 root root 4607 Jun 1 2015 sshd_config 541908 8 -rw-r----- 1 root root 4530 Sep 9 16:10 sshd_config.install Can anybody explain to me ? Thanks in advance Kindly regards +-----------------------------------------------------------+ | Marianne Frerichs | | Juelich Supercomputing Centre (JSC) | | Institute for Advanced Simulation (IAS) | | Forschungszentrum Juelich GmbH | | Email: M.Frerichs(a)fz-juelich.de | +-----------------------------------------------------------+ ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Forschungszentrum Juelich GmbH 52425 Juelich Sitz der Gesellschaft: Juelich Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher Geschaeftsfuehrung: Prof. Dr.-Ing. Wolfgang Marquardt (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 2