- openSUSE Autoinstall

[opensuse-autoinstall] 11.4: Problem with postinstallscript for fixing the second-stage-bug
by Daniel Spannbauer 26 Jun '12

26 Jun '12

Hello, I try to install a system opensuse 11.4 with autoyast. To "fix" the rpmcopy_secondstage_bug I run the following script in chroot: --------------------------------------- <script>  <chrooted config:type="boolean">true</chrooted> <filename>fix_postinstall_bug.sh</filename> <interpreter>shell</interpreter> <source><![CDATA[#!/bin/bash ( while [ ! -f /var/lib/YaST2/installation_disabled_steps ]; do sleep 1 done cp /var/lib/YaST2/installation_disabled_steps /var/lib/YaST2/installation_disabled_steps.bkp cat /var/lib/YaST2/installation_disabled_steps.bkp | grep -v "rpmcopy_secondstage" > /var/lib/YaST2/installation_disabled_steps) &]]> </source> </script> --------------------------------------------------------- The script is called during the installation but it seems that it is abborted before the file installation_disabled_steps is generated. The log shows: ------------------------------ 2012-06-05 04:48:10 <1> instze32(3283) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Calling YaST client autoinst_scripts2_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/autoinst_scripts2_finish.ycp:33 starting autoinst_scripts2_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] AutoinstScripts.ycp:715 Writing chroot script into /var/adm/autoinstall/scripts/fix_postinstall_bug.sh 2012-06-05 04:48:10 <1> instze32(3283) [YCP] AutoinstScripts.ycp:766 Script Execution command: /bin/sh -x /var/adm/autoinstall/scripts/fix_postinstall_bug.sh 2&> /var/adm/autoinstall/logs/fix_postinstall_bug.sh.log 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/autoinst_scripts2_finish.ycp:58 autoinst_scripts2_finish finished 2012-06-05 04:48:10 <1> instze32(3283) [Interpreter] clients/autoinst_scripts2_finish.ycp:58 Called YaST client returned. 2012-06-05 04:48:10 <1> instze32(3283) [wfm] Y2CCWFM.cc(createInLevel):148 Parsing finished 2012-06-05 04:48:10 <1> instze32(3283) [Interpreter] clients/installation_settings_finish.ycp:108 Calling YaST client installation_settings_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/installation_settings_finish.ycp:29 starting installation_settings_finish 2012-06-05 04:48:10 <1> instze32(3283) [YCP] clients/installation_settings_finish.ycp:44 Writing disabled modules ["system_analysis", "update_partition_auto", "add-on", "productsources", "user", "user_non_interactive", "auth", "initialization", "netprobe", "rpmcopy_secondstage", "hostname", "ask_net_test", "do_net_test", "addon_update_sources", "extrasources", "ask_online_update", "you", "restore_settings", "release_notes", "save_hardware_status", "congratulate", "lan", "disks_activate"] into /var/lib/YaST2/installation_disabled_steps --------------------------------------- Any hints about that? Regards Daniel + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 + '[' '!' -f /var/lib/YaST2/installation_disabled_steps ']' + sleep 1 ---------------------------------- Thats all..... In y2log you can see that the installaion_disabled_steps is generated after the scripts can do their job.... ------------------------------- -- Daniel Spannbauer Software Entwicklung 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

4 5

[opensuse-autoinstall] openSUSE 12.2 and autoyast-configured services
by Conny Seidel 25 Jun '12

25 Jun '12

Hello list, I'm having diufficulties enabling systemd services in openSUSE 12.2 from the autoyast file. Our current way doesn't work anymore: <runlevel> <default>3</default> <services config:type="list"> <service> <service_name>rpcbind</service_name> <service_status>enable</service_status> </service> </services> </runlevel> At least not for rpcbind. My workaround currently is to use a post-script to do a "systemctl enable rpcbind.service". -- Kind regards. Conny Seidel ################################################################## # Email : conny.seidel(a)amd.com GnuPG-Key : 0xA6AB055D # # Fingerprint: 17C4 5DB2 7C4C C1C7 1452 8148 F139 7C09 A6AB 055D # ################################################################## # Advanced Micro Devices GmbH Einsteinring 24 85609 Dornach # # General Managers: Alberto Bozzo # # Registration: Dornach, Landkr. Muenchen; Registerger. Muenchen # # HRB Nr. 43632 # ##################################################################

1 0

[opensuse-autoinstall] udev rules PCI based for nics
by Jochen Schaefer 20 Jun '12

20 Jun '12

Hi, is it possible to instruct autoyast to use pci based udev rules for network interfaces without specifying the pci ID's? I would like to have a statement like: <udev_rules><net_pci>yes</net_pci></udev_rules> To find out the pci_ids for a lot of machines is not very handy. We already have a script automation which does that step in the pre-script stage but would like to get rid of that and hand over this task to the installer logic. Thanks, Jochen -- 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] RE: Boot-loader on 2 DIsks?
by Stefan Lijewski 18 Jun '12

18 Jun '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 > But what about the bootloader? Can I install it on both disks by > autoyast? Mostly I set up software raid 1 using autoyast, but to install bootloader I'm using simple post-instalation script: rm /boot/grub/device.map cat /etc/grub.conf | /usr/sbin/grub --batch whet /etc/grub.conf is file which I provide with content: setup --stage2=/boot/grub/stage2 (hd0) (hd0,0) setup --stage2=/boot/grub/stage2 (hd1) (hd1,0) quit Will be nice to see how it can be done by autoyast. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iF4EAREIAAYFAk/YHNYACgkQwdp0CbGQFuKjDQEAlGEQi6x6HLTKgpY4W94MQ4H8 PHN/0rFUqzyOZUB31yQA/A3k6T09LvQygorjg4StOxDtUbmKBgRBsJQcWVNyU8BX =hUDH -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

2 1

[opensuse-autoinstall] Perpare second disk only if existent
by Daniel Spannbauer 15 Jun '12

15 Jun '12

Hello, I have to install some machines. Some of them have a second disk. Can this be done by one autoyast-profile (if the second disk is there..prepare it)? Or do I have to create to of them? Regards Daniel -- Daniel Spannbauer Software Entwicklung 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

1 0

[opensuse-autoinstall] Boot-loader on 2 DIsks?
by Daniel Spannbauer 12 Jun '12

12 Jun '12

Hello, I try to install a system with 2 Disks, Disk2 is mounted on Disk1, files are synced from disk A to disk B, so both disks should have the same files. If one disk fails it can be disabled in the bios-settings and the system can boot from the other harddisk.... But what about the bootloader? Can I install it on both disks by autoyast? Regards Daniel -- Daniel Spannbauer Software Entwicklung 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

1 0

[opensuse-autoinstall] led display Suppliers shared photos with you
by led display Suppliers 10 Jun '12

10 Jun '12

Dear Mr/Miss, Still be puzzling about looking for best led display supplier? Now it will be miles easier working with KEROSA! Here you can find competitive price and excellent quality with a best mix. We"ve been in led display career for many years. We know your market and your country well. Our business is flexible which something is more likely to be a friend chat. We never waste your time. Our conversation will be very efficient base on our good communication. Please reply as soon as possible .if you are working on some led display project. We are ready to make you a satisfied offer! Samuel Shezhen Krosa Techology Co.,Ltd. Address: Building 3,Park,Guanguang road,Bao"an District,Shenzhen,China. post 518000

1 0

[opensuse-autoinstall] YaST (incl. AutoYaST) is on github now
by Uwe Gansert 18 May '12

18 May '12

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

1 0

Antw: Re: [opensuse-autoinstall] problem installing from dhcp an two netcards
by Jochen Schaefer 17 May '12

17 May '12

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

1 0

Re: [opensuse-autoinstall] problem installing from dhcp an two netcards
by 686f6c6d 17 May '12

17 May '12

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

1 0