openSUSE Autoinstall July 2014

autoinstall@lists.opensuse.org

6 participants
5 discussions

[opensuse-autoinstall] State of Autoyast for OpenSUSE 13.1

by Joschi Brauchle

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 years, 10 months

[opensuse-autoinstall] [13.1] Bootloader timeout not working for grub 2?

by Robert Munteanu

Hi, I have the following snippet used to configure the bootloader <bootloader> <loader_type>grub2</loader_type> <global> <timeout config:type="integer">1</timeout> </global> </bootloader> However, the timeout is not changed, I can see that /etc/default/grub has the value GRUB_TIMEOUT=8 Changing that value to 1 and running grub2-mkconfig fixes the timeout problem. Is this feature not yet implemented for grub2 or am I using it incorrectly? Thanks, Robert -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

7 years, 2 months

[opensuse-autoinstall] [13.1] Creating a file in the user's home

by Robert Munteanu

Hi, As part of my autoinst.xml file I want to place a file in a specific user's home. Initially I tried to do it with a post-script, but that failed since the user's home was not yet created <script> <filename>post-install-vagrant-ssh-key</filename> <network_needed config:type="boolean">true</network_needed> <source><![CDATA[#!/bin/bash cd /home/vagrant mkdir -m 700 .ssh curl -o .ssh/authorized_keys 'https://raw.github.com/mitchellh/vagrant/master/keys/vagrant.pub' chmod 600 .ssh/authorized_keys chown -R vagrant .ssh ]]> </source> </script> I also tried using files/file section, but that seemed be completely ignored. According to [1] this should work without any issues in 13.1. <files> <file> <file_path>/home/vagrant/.ssh/authorized_keys</file_path>  <file_contents><![CDATA[ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6NF8iallvQVp22WDkTkyrtvp9eWW6A8YVr+kz4TjGYe7gHzIw+niNltGEFHzD8+v1I2YJ6oXevct1YeS0o9HZyN1Q9qgCgzUFtdOKLv6IedplqoPkcmF0aYet2PkEDo3MlTBckFXPITAMzF8dJSIFo9D8HfdOV0IAdx4O7PtixWKn5y2hMNG0zQPyUecp4pzC6kivAIhyfHilFR61RGL+GPXQ2MWZWFYbAGjyiYJnAmCP3NOTd0jMZEnDkbUvxhMmBYSdETk1rRgm+R4LOzFUGaHqHDLKLX+FIPKcF96hrucXzcWyLbIbEgE98OHlnVYCzRdK8jlqm8tehUc9c9WhQ== vagrant insecure public key]]></file_contents> <file_owner>vagrant</file_owner> <file_permissions>600</file_permissions> </file> </files> I tried both the file_contents and file_location variants ( one is commented out above ). What's the best way of placing a file in the user's home directory using autoinst.xml ? Thanks, Robert [1]: http://doc.opensuse.org/projects/autoyast/configuration.html#createprofile.… -- http://robert.muntea.nu/ -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

7 years, 2 months

[opensuse-autoinstall] Don't delete a partition, if it doesn't exist...create it.

by Daniel Spannbauer

Hello, some "strange" target for an autoinstallation.... We want a partition on the system to store some settings in it which should not be deleted at a new installation. If the partition is not there it should be created. Doesn't matter if the partition is at the beginning or the end of the harddisk. Any ideas how to do that? Regards Daniel -- Daniel Spannbauer Systemadministration marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email ds(a)marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

7 years, 3 months

[opensuse-autoinstall] specifying media URL for addon products

by Jochen Schaefer

Hi, I have a problem to specify the right media URL's for YUM repositories which are located on ISO images. Environment: virtual machine ESX - first cdrom: customized boot.iso - second cdrom: iso with YUM repositories (patches for SLES) - third cdrom: iso with original SLES11SP3 installation media boot prompt: install=cd:/?device=/dev/disk-by-label/SLES* autoyast=... addon-section points to cdrom with YUM repos: <media_url><![CDATA[cd:/sles11sp3_up/?device=/dev/disk/by-label/FPL-*]]></media_url> The result is that the installation process finds the correct installation media but cannot find the addon medias. The weird thing is when pointing the installation media to http://somewhere/sles11sp3 the addon product section works as expected - all installation sources are shown and used. But as soon as I specify the installation media from cdrom the addon products will not be found anymore. Could someone please point me to the error or provide the right specification? Thanks, Jochen

7 years, 3 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall July 2014