[opensuse-autoinstall] autoinstallation hangs at reboot
Dear AutoYaST crew , we have been using AutoYaST for installation of the last openSUSE distributions, but with 12.1 the unattended installation doesn't succeed anymore. The installation runs as usual with installing packages and writing system configuration. But at the end , shutting down is incomplete The last messages i see are: Es wird versucht , den installierten kernel mit kexec zu laden. Bitte warten Shutting down Name Service Cache Daemon Done On different clients the language was german or english. Then I see a black monitor with a colourful suse-green stripe at top and in the middle . Then the system hangs (even over night) If I do a manual hard shutdown and boot , the system comes up ( with trans replayed) with Kernel 3.1.0-1.2-desktop Asparagus and i see the known welcome window and "all seems right" . Our post.sh script was completely executed. To Prevent the hanging I looked for several workarounds for my XML-File , which was working fine for 11.3 1) <general> <mode> <confirm config:type="boolean">false</confirm> <reboot config:type="boolean">true</reboot> </mode> </general> I inserted a) <final_halt config:type="boolean">true</final_halt> --> same effect b) <halt config:type="boolean">false</halt> <forceboot config:type="boolean">true</forceboot> --> same effect c) <final_reboot config:type="boolean">true</final_reboot> --> same effect 2) I included: <software> <remove-packages config:type="list"> <package>systemd-sysvinit</package> </remove-packages> </software> --> same effect 3) <chroot-scripts config:type="list"> <script> <chrooted config:type="boolean">true</chrooted> <interpreter>shell</interpreter> <source><![CDATA[ insserv autoyast ]]></source> </script> </chroot-scripts> --> same effect 4 ) Some packages are explicitly added: <package>yast2-schema</package> <package>autoyast2</package> <package>yast2-slp</package>--> same effect <package>yast2-bootloader</package> <package>kexec-tools</package> --> same effect 5) I appended the boot-option for autointall ipv6.disable=1 --> same effect With the following boot-Options for Yast textmode=1 TERM=xterm the last operations are Master Record Control : switching to runlevel 5 .... Running /etc/init.d/before.local done Starting acpid Loading CPUFreq modules and system hangs over night Any help is appreciated. Marianne Frerichs ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Kennen Sie schon unsere app? http://www.fz-juelich.de/app -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
We had problems using the the GA ISO images of OpenSuse 12.1 for autoinstallation. Because of that we mirrored from gwdg the update and using this update during installation. The installation resource is named in the add_on_products section. The kernel version we use is: 3.1.9-1.4-desktop With this approach we had so far no further problems but i must mention that we use the old sysvinit-init for the services. Example of the autoinst.xml <profile xmlns="http://www.suse.com/1.0/yast2ns" xmlns:config="http://www.suse.com/1.0/configns"> <add-on> <add_on_products config:type="list"> <listentry> <media_url>http://w.x.y.z/export/mirror/stable/ftp5.gwdg.de/pub/opensuse/update/12.1</media_url> <product>SuSE-Linux-Updates</product> <product_dir>/</product_dir> <ask_on_error config:type="boolean">true</ask_on_error> <name>SuSE-Linux-Updates</name> </listentry> </add_on_products> </add-on> ... <software> <packages config:type="list"> <package>autoyast2</package> <package>sysvinit-init</package> ... Hth Hajo -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Thu, Mar 22, 2012 at 14:32, m.frerichs <m.frerichs@fz-juelich.de> wrote:
Dear AutoYaST crew ,
we have been using AutoYaST for installation of the last openSUSE distributions, but with 12.1 the unattended installation doesn't succeed anymore.
The installation runs as usual with installing packages and writing system configuration. But at the end , shutting down is incomplete [...] If I do a manual hard shutdown and boot , the system comes up ( with trans replayed) with Kernel 3.1.0-1.2-desktop Asparagus and i see the known welcome window and "all seems right" . Our post.sh script was completely executed.
Have you tried both 2) removing the systemd-sysvinit and 3) including the chroot-script to "insserv autoyast" at the same time? Are you using a particular large number of remove-packages, or a particular small number of patterns? (Maybe you are still missing one of the yast2* packages that provide the missing functionality.) Have you verified your profile? To do so, you can 1. run "yast autoyast" on your "profile server", 2. open your profile, and then 3. run "Tools" -> "Check Validity of Profile" (semi-useful because there are a lot of false positives, YMMV) and 4. check your software selection for conflicts or missing packages under "Group: Software" -> "Package Selection" -> "Edit" -> "Dependencies" -> "Check Dependencies Now", and finally 5. (I highly recommend this!) save your profile to another filename and diff it against the file you loaded, to make sure your syntax is up-to-date. (If you had package conflicts, you can also check this after installation in /var/log/YaST2/badlist) -- HTH 686f6c6d / Christopher "m4z" Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
Hello , hurra , i succeeded to autoinstall a 12.1-client after i explicitly umounted some filesystems at the end of post.sh which i had mounted in it . ( i did this withount umount for instalaltion of 11.3 without irritation) But many questions remain because of error messages in my xml-file, see downwards. In my script after installation the addition of many repos and " zypper in " of hundreds of rpms took a long , long time of several hours , which normally was executed in less then 1 hour in 11.3. I shortened this process by adding ipv6.disable=1 in the bootoptions. Where can i lay this down in the xml-File and in /etc/sysconfig ? Many thanks to Christopher "m4z" Holm for his hints. Marianne Frerichs Have you tried both 2) removing the systemd-sysvinit and 3) including the chroot-script to "insserv autoyast" at the same time? yes , both was configured at the same time
Are you using a particular large number of remove-packages, or a particular small number of patterns? (Maybe you are still missing one of the yast2* packages that provide the missing functionality.) I normally expect that all neccessary functions are collected in yast2_basis i installed this: <pattern>yast2_basis</pattern> <pattern>yast2_basis-32bit</pattern> <pattern>yast2_install_wf</pattern> <pattern>yast2_install_wf-32bit</pattern> <pattern>kde4_yast</pattern> <pattern>kde4_yast-32bit</pattern> <package>yast2-schema</package> <package>autoyast2</package> <package>yast2-slp</package> <package>yast2-bootloader</package> <package>yast2-online-update-configuration</package> <package>yast2-firstboot</package>
Have you verified your profile? To do so, you can 1. run "yast autoyast" on your "profile server", 2. open your profile, and then 3. run "Tools" -> "Check Validity of Profile" (semi-useful because there are a lot of false positives, YMMV) and 4. check your software selection for conflicts or missing packages under "Group: Software" -> "Package Selection" -> "Edit" -> "Dependencies" -> "Check Dependencies Now", and finally 5. (I highly recommend this!) save your profile to another filename and diff it against the file you loaded, to make sure your syntax is up-to-date. it is curious: even if i succeed in installation i get error messages in my xml-File
* Section bootloader: Error * Section chroot-scripts: Error * Section deploy_image: OK * Section general: Error * Section groups: OK * Section keyboard: OK * Section language: OK * Section login_settings: OK * Section networking: Error * Section nfs: OK * Section nis: OK * Section partitioning: Error * Section report: OK * Section runlevels: Error * Section scripts: OK * Section software: Error * Section sysconfig: OK * Section timezone: OK * Section user_defaults: Error * Section users: OK * Section x11: Error /usr/bin/xmllint --noout --relaxng /usr/share/YaST2/schema/autoyast/rng/profile.rng /tmp/YaST2-13674-aSXamr/bootloader.xml /tmp/YaST2-13674-aSXamr/bootloader.xml:4: element bootloader: Relax-NG validity error : Element profile has extra content: bootloader /tmp/YaST2-13674-aSXamr/bootloader.xml fails to validate and same for all "error" sections There are no former explanations and i can see nothing wrong in my appended XML-File
(If you had package conflicts, you can also check this after installation in /var/log/YaST2/badlist)
There was no such file ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ 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. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt ------------------------------------------------------------------------------------------------ ------------------------------------------------------------------------------------------------ Kennen Sie schon unsere app? http://www.fz-juelich.de/app
On Thu, Mar 29, 2012 at 12:41, m.frerichs <m.frerichs@fz-juelich.de> wrote:
Hello ,
hurra , i succeeded to autoinstall a 12.1-client
after i explicitly umounted some filesystems at the end of post.sh which i had mounted in it . ( i did this withount umount for instalaltion of 11.3 without irritation)
So the initial problem with autoyast not rebooting is solved? Great!
But many questions remain because of error messages in my xml-file, see downwards.
In my script after installation the addition of many repos and " zypper in " of hundreds of rpms took a long , long time of several hours , which normally was executed in less then 1 hour in 11.3.
Is there a reason you don't use the <add-on> section to add the repos? (From your profile I assume they live on NFS/SMB and are run in the post script.) But I don't assume that would improve the install speed in any way.
I shortened this process by adding ipv6.disable=1 in the bootoptions.
Where can i lay this down in the xml-File and in /etc/sysconfig ?
Not sure if there is a better way via <sysconfig>, but in general - you need to uncomment/set "net.ipv6.conf.all.disable_ipv6 = 1" in /etc/sysctl.conf - BUT ipv6 would then still be enabled in autoyast's stage1 (AFAICT), - so you'd still have to type "ipv6.disable=1" at the boot prompt (or create a custom boot media, including the boot options, to avoid that).
Many thanks to Christopher "m4z" Holm for his hints.
You're welcome! I've been helped countless times myself. It's a ciiiircle -- shut up, Lion King! (;
Are you using a particular large number of remove-packages, or a particular small number of patterns? (Maybe you are still missing one of the yast2* packages that provide the missing functionality.) I normally expect that all neccessary functions are collected in yast2_basis i installed this: [...]
Are there still remaining problems with the packages/behavior, or was everything solved by umounting?
3. run "Tools" -> "Check Validity of Profile" (semi-useful because there are a lot of false positives, YMMV) and
it is curious: even if i succeed in installation i get error messages in my xml-File
* Section bootloader: Error * Section chroot-scripts: Error * Section deploy_image: OK * Section general: Error [...]
and same for all "error" sections
There are no former explanations and i can see nothing wrong in my appended XML-File
I would assume those are false positives then. I see lots of them, too, even when the profile was created entirely by "yast autoyast". IIRC there was bug report or thread on this ML about the schema files being outdated, so don't be confused by these errors as long as everything is fine. Another way to debug this, apart from saving to another filename in yast and then diffing (as described in my last mail), would be to diff the profile on the server with the profile on the installed machine after successful installation (/var/adm/autoinstall/cache/installedSystem.xml or so). But again, as long as there are no problems, there's no need to do that.
(If you had package conflicts, you can also check this after installation in /var/log/YaST2/badlist)
There was no such file
That is a good thing, it means there were no package conflicts. I didn't make myself clear enough: The file exists *only* when there were errors/conflicts. -- Kind regards 686f6c6d / Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
On Mon, Apr 2, 2012 at 14:30, 686f6c6d <686f6c6d@googlemail.com> wrote:
I shortened this process by adding ipv6.disable=1 in the bootoptions.
Where can i lay this down in the xml-File and in /etc/sysconfig ?
Not sure if there is a better way via <sysconfig>, but in general - you need to uncomment/set "net.ipv6.conf.all.disable_ipv6 = 1" in /etc/sysctl.conf - BUT ipv6 would then still be enabled in autoyast's stage1 (AFAICT), - so you'd still have to type "ipv6.disable=1" at the boot prompt (or create a custom boot media, including the boot options, to avoid that).
Stupid me forgot the code: ---------- 8< ---------- <post-scripts config:type="list"> <script> <debug config:type="boolean">true</debug> <feedback config:type="boolean">false</feedback> <filename>ipv6sysctl</filename> <interpreter>shell</interpreter> <network_needed config:type="boolean">false</network_needed> <source><![CDATA[cp /etc/sysctl.conf /etc/sysctl.conf.backup sed -e "s/# \(net\.ipv6\.conf\.all\.disable_ipv6 = 1\)/\1/" /etc/sysctl.conf.backup > /etc/sysctl.conf rm /etc/sysctl.conf.backup ]]></source> </script> </post-scripts> ---------- >8 ---------- -- Kind regards 686f6c6d / Christopher 'm4z' Holm -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-autoinstall+owner@opensuse.org
participants (3)
-
686f6c6d -
Hans-Joachim Ehlers -
m.frerichs