[Bug 803577] New: User initscripts are exiting arbitrarily and final reboot is canceled
https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c0 Summary: User initscripts are exiting arbitrarily and final reboot is canceled Classification: openSUSE Product: openSUSE Factory Version: 12.3 Beta 1 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: fehr@suse.com ReportedBy: joschibrauchle@gmx.de QAContact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.70 Safari/537.17 On an openSUSE 12.3 RC1 AY installation, I am running a user init-script like this: ---------- <scripts> <init-scripts config:type="list"> <script> <filename>init0000_final_installation.sh</filename> <location><![CDATA[nfs://gemini.lnt.ei.tum.de/ha/export/install/linux/opensuse/12.3/autoinstall/scripts/init0000_final_installation.sh]]></location> </script> ... some more scripts </init-scripts> </script> ---------- plus a final reboot is configured: ---------- <general> <mode> <confirm config:type="boolean">false</confirm> <final_reboot config:type="boolean">true</final_reboot> </mode> </general> ---------- The init0000 script is executed, but exists at arbitrary positions in the script... (possibly due to calls to systemctl inside the init script? see code attached). After init0000 script exited prematurely, all other following init scripts are not being executed, as well as the final reboot is not happening. It looks like the whole process tree running the init scripts just quits. Reproducible: Always Steps to Reproduce: 1. AY installation with init scripts 2. init script makes calls to systemctl Actual Results: init script exits before finishing, all other init scripts get lost (incl final reboot) Expected Results: init scripts should run successfully (or maybe fail), but all scripts should be run, independent of exit code. -- 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#c1 --- Comment #1 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-02-13 17:30:19 UTC --- Created an attachment (id=524520) --> (http://bugzilla.novell.com/attachment.cgi?id=524520) Init script in question, calling systemctl from within -- 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#c2 --- Comment #2 from Joschi Brauchle <joschibrauchle@gmx.de> 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#c3 --- Comment #3 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-02-13 17:38:43 UTC --- The logfile attached shows that it quits after running "systemctl start network.service". Actually, it does not quit at this line all the time, but rather at some random "systemctl" line later on. I think it never gets beyond the systemctl calls... -- 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 <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX --- Comment #4 from Thomas Fehr <fehr@suse.com> 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#c Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|AutoYaST |AutoYaST Version|12.3 Beta 1 |RC 1 Product|openSUSE Factory |openSUSE 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#c5 Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | --- Comment #5 from Joschi Brauchle <joschibrauchle@gmx.de> 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#c Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO InfoProvider| |joschibrauchle@gmx.de -- 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 <fehr@suse.com> 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#c Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |769924 -- 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 <walter.zimmer@dlr.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |walter.zimmer@dlr.de --- Comment #7 from Walter Zimmer <walter.zimmer@dlr.de> 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#c8 --- Comment #8 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-02-15 13:45:13 UTC ---
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!
For 12.3, the autoyast init script was converted by a systemd service with exactly those parameters, see https://bugzilla.novell.com/show_bug.cgi?id=788997 -- 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#c9 Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED InfoProvider|joschibrauchle@gmx.de | --- Comment #9 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-02-20 07:15:56 UTC --- Since bnc#769924 has been resolved, there have been no more problems with the init scripts on our end (so far). -- 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 <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |CLOSED Resolution| |FIXED --- Comment #10 from Joschi Brauchle <joschibrauchle@gmx.de> 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#c11 Joschi Brauchle <joschibrauchle@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |REOPENED Version|RC 1 |RC 2 Resolution|FIXED | --- Comment #11 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-02-28 12:27:10 UTC --- During a test installation with RC2 the problem just appeared again. The init script failed to run completely but exited in the middle of a command. All systemd related calls have been removed from the init script. I highly suspect systemd to kill the init script for some reason. Is there any way I can put systemd in some kind of debug/verbose mode in YaST stage2 to see what it is doing?!? -- 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 <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fehr@suse.com AssignedTo|fehr@suse.com |fcrozat@suse.com --- Comment #12 from Thomas Fehr <fehr@suse.com> 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#c13 --- Comment #13 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-03-01 12:38:58 UTC --- Please see attached systemd logs.
From what I can see, it looks like the init scripts get killed. I dont know the reason though...
... [10606.990126] systemd[1]: Job YaST2-Second-Stage.service/start finished, result=done [10606.990253] systemd[1]: Started YaST2 Second Stage. [10606.990371] systemd[1]: Got SIGCHLD for process 3098 (plymouth) [10606.990403] systemd[1]: Child 3098 died (code=exited, status=0/SUCCESS) [10606.990405] systemd[1]: Child 3098 belongs to autoyast-initscripts.service [10606.990417] systemd[1]: autoyast-initscripts.service: control process exited, code=exited status=0 [10606.996126] systemd[1]: autoyast-initscripts.service got final SIGCHLD for state start-pre [10606.996161] systemd[1]: About to execute /usr/lib/YaST2/bin/autoyast-initscripts.sh [10606.996317] systemd[1]: Forked /usr/lib/YaST2/bin/autoyast-initscripts.sh as 3070 [10607.006209] systemd[1]: autoyast-initscripts.service changed start-pre -> start ... [10607.040489] systemd[1]: Got D-Bus request: org.freedesktop.systemd1.Manager.Reload() on /org/freedesktop/systemd1 [10607.040498] systemd[1]: Reloading. ... [10607.065209] systemd[1]: Reinstalled deserialized job autoyast-initscripts.service/start as 109 ... [10607.066199] systemd[1]: autoyast-initscripts.service changed dead -> start ... [10612.020558] systemd[1]: Received SIGCHLD from PID 3070 (autoyast-initsc). [10612.020577] systemd[1]: Got SIGCHLD for process 3070 (autoyast-initsc) [10612.020613] systemd[1]: Child 3070 died (code=killed, status=1/HUP) [10612.020616] systemd[1]: Child 3070 belongs to autoyast-initscripts.service [10612.020643] systemd[1]: autoyast-initscripts.service: main process exited, code=killed, status=1/HUP [10612.020683] systemd[1]: autoyast-initscripts.service changed start -> exited [10612.020695] systemd[1]: Job autoyast-initscripts.service/start finished, result=done [10612.020707] systemd[1]: Started Autoyast2 Init Scripts. --------------- -- 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 <joschibrauchle@gmx.de> 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#c15 --- Comment #15 from Frederic Crozat <fcrozat@suse.com> 2013-03-11 16:00:48 UTC --- If the initscript is taking a very long time to start (or is in a deadlock), you might need to disable timeout in the systemd service file by adding TimeoutSec=0 in autoyast-initscripts.service (in [Service] section). -- 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 <fehr@suse.com> 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#c17 --- Comment #17 from Frederic Crozat <fcrozat@suse.com> 2013-03-11 16:37:24 UTC --- (In reply to comment #16)
So "TimeoutSec=0" is there. Do you see something different?
I don't maintain nor package autoyast, so I wasn't sure if disabling timeout was enforced or not. Without knowning what is done by the script, it will be hard to tell what is at fault.. -- 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#c18 --- Comment #18 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-03-24 15:17:18 UTC --- I *think* I've found the problem: It seems to be the "StandardInput=tty" line in the service file. I guess what happens is that after YaST stage 2 finishes, systemd restarts all getty's and kills all existing ones (possibly due to the "isolate graphical.target" call, but maybe not). This behavior is definitely correct as during installation all TTYs are root shells. So now due to the "StandardInput=tty", the initscripts get signaled a HUP when the getty's are restarting. Hence I patched the /usr/lib/systemd/system/autoyast-initscripts.service file like so: ---------- --- a/autoyast-initscripts.service 2013-03-14 19:31:19.000000000 +0100 +++ b/autoyast-initscripts.service 2013-03-24 16:12:01.412201230 +0100 @@ -4,12 +4,10 @@ [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 ---------- and so far, all installations (~5) have worked as expected. I also chose to remove the "Environment" line, because I think setting "SYSTEMD_NO_WRAP=1" is not good here... A user would expect calls to rcscripts to behave like in the installed system, i.e., to be wrapped by systemd by default. -- 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#c19 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #19 from Thomas Fehr <fehr@suse.com> 2013-03-25 10:39:34 UTC --- Thank you very much for investigating this. I integrated your suggested changes to git repo. -- 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 <fcrozat@suse.com> 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#c21 --- Comment #21 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-03-25 11:01:19 UTC --- (In reply to comment #20)
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.
Of course that was just a suggestion on my part. I would assume it is OK to remove this here, because the mentioned service runs a bash script in the installed/final system, i.e., after YaST is completely done and the system has booted and is up and running. But you may be right: If a user calls systemctl from inside one of these scripts, a deadlock could occur... -- 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 <walter.zimmer@dlr.de> 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#c23 --- Comment #23 from Joschi Brauchle <joschibrauchle@gmx.de> 2013-04-09 13:01:08 UTC --- Hello Walter, I currently use a chroot script to workaround this and bnc#811688: ---------------- <scripts> <chroot-scripts config:type="list"> <script> <filename>chroot_workaround_803577_and_811688.sh</filename> <source><![CDATA[#!/bin/bash # Work around for BNC#803577 sed -i 's/^Environment=.*/Environment=TERM=linux/' /mnt/usr/lib/systemd/system/autoyast-initscripts.service sed -i 's/^StandardInput=.*//' /mnt/usr/lib/systemd/system/autoyast-initscripts.service # Work around for BNC#811688 sed -i 's/^After=.*/After=default.target/' /mnt/usr/lib/systemd/system/autoyast-initscripts.service]]> </source> </script> </chroot-scripts> </scripts> ---------------- The third 'sed' line is for bnc#811688. I thought I'd add it here as well so that you get a completely working service file... -- 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 <fehr@suse.com> 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#c25 --- Comment #25 from Walter Zimmer <walter.zimmer@dlr.de> 2013-04-09 13:22:08 UTC --- Thanks, I really appreciate that you care also about the blind! -- 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 <bwiedemann@suse.com> 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.
https://bugzilla.novell.com/show_bug.cgi?id=803577 https://bugzilla.novell.com/show_bug.cgi?id=803577#c27 --- Comment #27 from Swamp Workflow Management <swamp@suse.de> 2013-06-10 10:30:02 UTC --- openSUSE-RU-2013:0987-1: An update that has three recommended fixes can now be installed. Category: recommended (low) Bug References: 565557,803577,811688 CVE References: Sources used: openSUSE 12.3 (src): autoyast2-2.23.6-1.4.1 -- 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.
participants (1)
-
bugzilla_noreply＠novell.com