https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c2 --- Comment #2 from Joschi Brauchle 2013-02-13 17:36:48 UTC --- Created an attachment (id=524521) --> (http://bugzilla.novell.com/attachment.cgi?id=524521) Logfile of init0000, showing that it did not finish -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c4 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #4 from Thomas Fehr 2013-02-13 18:06:10 UTC --- I converted autoyast init script handling after beta#1 to use a systemd.service (this move caused bnc#803036). So there is not much sense in debugging state of beta#1. Wait for RC2 or apply fixes from github for bnc#803036 to RC1. Please reopen if the problem still exists in RC2. About the problem itself, maybe system is simply confused when it gets calls to systemctl from inside systemd services (and autoyast init scripts are executed from /etc/init.d/autoyast which is handled by systemd). If this is the case, there is not much autoyast can do. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c5 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #5 from Joschi Brauchle 2013-02-13 22:00:12 UTC --- Yes, of course you are right! The problem exists with RC1+ (which includes your init script fixes)... I filed against the wrong version, sorry! So the argument with systemd being confused when it gets calls to itself from inside a service makes sense... But then again, isn't YaST2 stage 2 itself simply started as a systemd service and makes calls to systemd as well? I would like to do some further debugging on what causes the script execution to be cancelled. Hence, I reopened and will report back. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c6 --- Comment #6 from Thomas Fehr 2013-02-14 11:56:40 UTC --- Normally yast should not do too much calls to systemd at this stage. I am currently working on bnc#769924 and also run into problems that yast gets killed by something (I strongly assume systemd) when I issue certain systemctl commands. But this can be easily checked by temporarily removing the systemctl calls from your script and check if the killing stops. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c7 Walter Zimmer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |walter.zimmer@dlr.de --- Comment #7 from Walter Zimmer 2013-02-15 13:14:54 UTC --- I'm currently creating autoinstall scripts for 12.2, and I wondered why my very long initscript (30min installing stuff) is always executed again after reboot. It seems that systemd kills the autoyast service after 90 seconds, just as stated in the systemd documentation. The script itself finished successfully according to the log, but as autoyast cannot do the "mv" of the script, it is executed again after the next boot. Here the systemctl output while the script is still running: # systemctl status autoyast.service autoyast.service - LSB: A start script to execute autoyast scripts Loaded: loaded (/etc/init.d/autoyast) Active: failed (Result: timeout) since Fri, 15 Feb 2013 13:13:06 +0100; 57min ago Process: 8689 ExecStart=/etc/init.d/autoyast start (code=killed, signal=TERM) CGroup: name=systemd:/system/autoyast.service So maybe it is a good idea to set the type to oneshot or set the timeout to 0? It would be great if this could be fixed for 12.3! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c Bug 803577 depends on bug 769924, which changed state. Bug 769924 Summary: the autoyast runlevel config kicks in after reboot only with systemd http://bugzilla.novell.com/show_bug.cgi?id=769924 What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Status|ASSIGNED |RESOLVED Resolution| |FIXED -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c10 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |FIXED --- Comment #10 from Joschi Brauchle 2013-02-20 07:16:40 UTC --- Closing due to comment #9. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c12 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com AssignedTo|fehr@suse.com |fcrozat@suse.com --- Comment #12 from Thomas Fehr 2013-02-28 13:09:17 UTC --- You can get debug output from systemd by adding "systemd.log_level=debug systemd.log_target=kmsg" to kernel command line. The logs can be looked at by "dmesg" afterwards Reassigned to systemd maintainer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c14 --- Comment #14 from Joschi Brauchle 2013-03-01 12:40:45 UTC --- Created an attachment (id=527712) --> (http://bugzilla.novell.com/attachment.cgi?id=527712) systemd logs -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c16 --- Comment #16 from Thomas Fehr 2013-03-11 16:31:34 UTC --- I created autoyast-initscripts.service according to your advise in bnc#788997 comment#2. If my editor does not betray me, the file /usr/lib/systemd/system/autoyast-initscripts.service contains the following: --------------------------------------------------------------------------------------------------------- [Unit] Description=Autoyast2 Init Scripts After=remote-fs.target network.target time-sync.target mail-transfer-agent.target hwscan.service ypbind.service [Service] Type=oneshot Environment=SYSTEMD_NO_WRAP=1 TERM=linux ExecStartPre=-/usr/bin/plymouth --hide-splash ExecStart=/usr/lib/YaST2/bin/autoyast-initscripts.sh RemainAfterExit=yes TimeoutSec=0 StandardInput=tty [Install] WantedBy=default.target --------------------------------------------------------------------------------------------------------- So "TimeoutSec=0" is there. Do you see something different? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c20 --- Comment #20 from Frederic Crozat 2013-03-25 10:45:17 UTC --- (In reply to comment #19)

Thank you very much for investigating this. I integrated your suggested changes to git repo.

Guys, be careful with removing "SYSTEMD_NO_WRAP=1", it might cause some breakage. I would suggest to replace this with "SYSTEMCTL_OPTIONS=--ignore-dependencies" to follow the change which was done on YaST2-Second-Stage. Otherwise you might end-up in deadlock. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c22 --- Comment #22 from Walter Zimmer 2013-04-09 12:17:38 UTC --- Maybe a completely stupid question: how can I benefit from the fixing of this bug? I just installed completely new with the 12.3 (oss/non-oss/updates-oss/updates-non-oss) repos from yesterday and have, after install, the following file for systemd: /var/lib/systemd/system/autoyast-initscripts.service which is from 20.02.2013. I think this matches the package in the oss repository which is from 22.02.2013 However, in updates-oss, I find an updated systemd package to be from 27.03.2013, which supposedly carries the fixed files of this bug already. At installation time, I verified that it took packages from all four repositories, so they were included successfully. Maybe the updates are not applied for the packages yast uses for installation? Is there any other explanation for this observation? Is there anything else I should look at for making sure I get this update at installation time? Many thanks for any hints! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c24 --- Comment #24 from Thomas Fehr 2013-04-09 13:16:53 UTC --- (In reply to comment #22)

Maybe a completely stupid question: how can I benefit from the fixing of this bug? Not easily yet. The fix is currently in git repo but not in a release package.

I just installed completely new with the 12.3 (oss/non-oss/updates-oss/updates-non-oss) repos from yesterday and have, after install, the following file for systemd: /var/lib/systemd/system/autoyast-initscripts.service which is from 20.02.2013.

I think this matches the package in the oss repository which is from 22.02.2013

However, in updates-oss, I find an updated systemd package to be from 27.03.2013, which supposedly carries the fixed files of this bug already.

No, file /usr/lib/systemd/system/autoyast-initscripts.service is part of package autoyast2-installation, so far there is no new package released for autoyast since 12.3 GA. I hope I can release one next week. The workaround suggested in comment#23 is fine until updated autoyast packages are released. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c26 --- Comment #26 from Bernhard Wiedemann 2013-04-16 13:00:22 CEST --- This is an autogenerated message for OBS integration: This bug (803577) was mentioned in https://build.opensuse.org/request/show/171057 Maintenance / -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.