- openSUSE Autoinstall

[opensuse-autoinstall] /tmp as tmpfs?
by Daniel Spannbauer 26 Sep '17

26 Sep '17

Hello, I try to configure /tmp as tmpfs...is that possible via autoyast? Or do I have to call a script which adds the line into the fstab? 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

2 2

[opensuse-autoinstall] Create own installation media
by Daniel Spannbauer 14 Sep '17

14 Sep '17

Hello, I try to create my own installationmedia for 42.3. It should contain the packages for the minimal installation and some self created packages. So I took an original Leap-Image, removed all packages and added my own files (also an autoinstall.xml) I create the package_descr (with create_package_descr), the MD5SUMs, directory.yast files, sha1sums and the content file. The content file is also signed and the exported keys are on that media. The installion for the minimal package selection works fine. But It can't find my own packages. Even when I add that repo zypper can't find it. When I created a AddOn-Image with the Yast AddOn creator and add this as repo the packages are found. But I have to do it all from a bash script so I cant use Yast here. What I'm doing wrong here? Any hints? How does Yast get the list of available packages? 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

1 0

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

11 Sep '17

On Mon, Sep 4, 2017 at 12:42 AM, Erico Mendonça <erico.mendonca(a)gmail.com> wrote: > Try netdevice=eth0 . > > > On Wed, Aug 16, 2017, 11:42 AM 686f6c6d <686f6c6d(a)googlemail.com> wrote: >> >> 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. […] >> Once we use the NET-flavour ISOs for our boot stick, it works as >> expected. Is this expected behaviour? Is it a known issue? Thanks for your reply, the result seems to be the same though, the interface does not come up… y2start does contain a line: […] declare -x netdevice="eth0" …but grepping "net\|eth" etc. from y2log only results in the two lines: […] install([…]) [Ruby] modules/NetworkService.rb:3{03,20}: IPv{4,6} network is not running ... /var/log/messages shows the correct commandline, the network card driver is loaded[0], but it is not brought up and no clue what might be wrong, "ip a" shows eth0 as DOWN. (When I additionally append "netsetup=1" to the boot parameters, autoyast prompts me whether to use DHCP (maybe that's expected, I don't know) and succeeds if I confirm.) Anything else I can do to debug this further? [0]: tested on two laptops: - Laptop 1 (Sony Vaio): kernel recognizes card as "r8169 Gigabit Ethernet driver 2.3LK-NAPI […]" (and AutoYAST as "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller\n drivers: r8169*") - Laptop 2 (Dell Latitude): kernel recognizes card as "Tigon3 [partno(BCM95761e) rev 5761100] (PCI Express)" (and AutoYAST as "Broadcom NetXtreme BCM5761e Gigabit Ethernet PCIe\n drivers: tg3*") -- 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"ddddd -- 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] Disabling FW during installation of SLES12
by Frieder Schmidt 06 Sep '17

06 Sep '17

Hi list, when doing an autoyast installation of SLES12 the firewall is active at the end of stage 2 but no interface is assigned to any zone blocking SSH access until the firewall is stopped or the newly installed server is rebooted (we do not need the firewall in our environment). This is different then in SLES11 and earlier versions where at the end of stage 2 the firewall is not active. Is there a way to have the firewall automatically stopped at the end of Stage 2 in SLES12 as well? Thanks in advance Frieder Mit freundlichen Grüßen Dr. Frieder Schmidt Principal Technical Specialist Lead Architect Infrastructure Solutions Micro Focus Location: Nördlicher Zubringer 9-11, 40470 Düsseldorf, Germany Tel.: +49 (0)211 - 5631 3760 Mobile: +49 (0)173 5876 677 ( tel:01735876666 ) Fax.: +49 (0)211 - 5631 3769 e-mail: Frieder.Schmidt(a)microfocus.com PLEASE NOTE: This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, distribution or other use by anyone else is strictly prohibited. If you are not an intended recipient, please contact the sender and delete all copies. Thank you. Attachmate Group Germany GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 202401 (AG München) -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 6

[opensuse-autoinstall] Passing path to autoyast-Profile
by Daniel Spannbauer 04 Sep '17

04 Sep '17

Hello, I'm creating a new installation-DVD with a Autoyast-Profile on ist. What ist the right way to provie the path to the autoyast profile? autoyast=cd://auoyast.xml Ist that correct? Regards Daniel -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org

3 3

[opensuse-autoinstall] strange boot problems
by Dr. Peer-Joachim Koch 04 Sep '17

04 Sep '17

Hi, I've noticed rare boot problems occurring on nodes installed via autoyast. Some machines of our HPC cluster, currently containing around 60 nodes, sometimes to not reboor correctly. So if the system crash OR I just enter "reboot" the system will not start again. Grub i working the boot process is starting and then the system remains in a waiting state after 8 sec (see boot5.jpg). The hard disk controller is loaded, the file system is clean - I have no idea what is blocking the system. For the normal nodes a reinstall using autoyast was the fastest solution. But maybe someone has an idea where to look for the problem ... I haven't noticed this behavior on nodes installed manually... -- 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 2

[opensuse-autoinstall] apparmor-docs is required....but not configured to install
by Daniel Spannbauer 01 Sep '17

01 Sep '17

Hello, I installed a Leap system by hand (minimal packages, Text-Only) and cloned that system to a autoyastprofile. I removed all unneeded packages from the installation source and started the installation again, but now via the created autoyast profile. Now, the installation process claims about a missing apparmor-doc-package. It is not needed by any package and is not configured in the autoyast file. Why is it searching for that packages? 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

1 0

Re: [opensuse-autoinstall] Bug while starting Autoyast
by Daniel Spannbauer 29 Aug '17

29 Aug '17

> Hello, > I will send you the profile via mail. > Atm I start the installation via network boot, I use the same profile. > Via network boot it seems to work. This information was wrong....it also doesn't work over network . 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

1 0

[opensuse-autoinstall] Bug while starting Autoyast
by Daniel Spannbauer 28 Aug '17

28 Aug '17

Hallo, now, i started the installationsystem with an autoyast parameter, the yast starts but cancles while importing my xml. Here are the messages from the logs: 2017-08-28 07:27:41 <3> instze32(3720) [Ruby] yast/wfm.rb:253 Client call failed with 'undefined method `fetch' for nil:NilClass' (NoMethodError) and backtrace ["/mounts/mp_0001/usr/share/YaST2/modules/AutoinstSoftware.rb:98:in `Import'", "/mounts/mp_0001/usr/share/YaST2/clients/inst_autosetup.rb:363:in `main'", "/mounts/mp_0001/usr/share/YaST2/clients/inst_autosetup.rb:523:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:195:in `CallFunction'", "/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1355:in `RunFrom'", "/mounts/mp_0001/usr/share/YaST2/modules/ProductControl.rb:1542:in `Run'", "/usr/share/YaST2/lib/installation/clients/inst_worker_initial.rb:106:in `main'", "/mounts/mp_0001/usr/share/YaST2/clients/inst_worker_initial.rb:2:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:195:in `CallFunction'", "/usr/share/YaST2/lib/installation/clients/installation.rb:77:in `main'", "/mounts/mp_0001/usr/share/YaST2/clients/installation.rb:2:in `<top (required)>'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `eval'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:300:in `run_client'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:206:in `call_builtin_wrapper'", "/usr/lib64/ruby/vendor_ruby/2.1.0/yast/wfm.rb:195:in `CallFunction'", "/usr/lib/YaST2/bin/y2start:56:in `<main>'"] 2017-08-28 07:27:41 <3> instze32(3720) [Ruby] yast/wfm.rb:275 Internal error. Please report a bug report with logs. Is it a known bug (I googled a bit but found nothing) or should I file a bug report about this? Or is it caused by a foulty xml? 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

2 2

[opensuse-autoinstall] Leap 42.3 and rules
by Werner Hack 16 Aug '17

16 Aug '17

Hi all, I use a rules file with several custom rules to install Leap 42.3 The rules worked fine in Leap 42.2. But in Leap 42.3... o I noticed that the result of the first rule is always ignored and therefore it is not merged. My workaroud to this I have to write a dummy rule at first place. o All my dialogboxes pop up a second time. This is annoying. How can I prevent this behaviour? Any idea what goes wrong here? Are these known bugs? Any solutions? What has changed since Leap 42.2? Regards Werner

2 1