[Bug 769924] New: the autoyast runlevel config kicks in after reboot only with systemd

newer
[Bug 804232] New: lxc: creating...

older
[Bug 800690] New: kdewebdev3 has...

bugzilla_noreply＠novell.com

4 Jul 2012 4 Jul '12

09:45

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c0 Summary: the autoyast runlevel config kicks in after reboot only with systemd Classification: openSUSE Product: openSUSE 12.2 Version: Beta 2 Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: AutoYaST AssignedTo: locilka@suse.com ReportedBy: ug@suse.com QAContact: qa-bugs@suse.de Found By: Customer Blocker: --- if you use systemd on 12.2 (on 12.1 too btw) and you have a runlevel config in the autoyast XML like: <runlevel> <default>3</default> <services config:type="list"> <service> apache2 enable </service> </services> </runlevel> the apache will not run after the autoinstallation. You have to reboot the machine and then it runs. I think the reason is that yast2-runlevel is configured in the 2nd stage and systemd does not start the service then when it's activated. The service is switched to "enabled" then but not to "running" at the end of the installation. I'm not a systemd expert but maybe there is an option like "enable and start"? If not, then we have to move the runlevel module to the first stage I'm afraid. -- 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.

Show replies by date

bugzilla_noreply＠novell.com

15 Nov 15 Nov

16:32

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c1 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |ASSIGNED --- Comment #1 from Lukas Ocilka 2012-11-15 16:32:12 UTC --- Starting enabled service if it fits the current runlevel (BNC #769924) https://github.com/kobliha/yast-runlevel/commit/ce9183bc0aca29cb2a099ffc15b4... -- 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.

bugzilla_noreply＠novell.com

16:37

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c2 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #2 from Lukas Ocilka 2012-11-15 16:37:46 UTC --- Fixed in yast2-runlevel-2.21.4 -- 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.

bugzilla_noreply＠novell.com

16:45

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c3 --- Comment #3 from Lukas Ocilka 2012-11-15 16:45:51 UTC --- osc submitrequest YaST:Head yast2-runlevel openSUSE:Factory created request id 141453 -- 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.

bugzilla_noreply＠novell.com

16 Nov 16 Nov

13:15

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c4 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joschibrauchle@gmx.de --- Comment #4 from Joschi Brauchle 2012-11-16 13:15:31 UTC --- Will this be available for 12.2? My 12.2 autoinstallation is affected by this problem... -- 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.

bugzilla_noreply＠novell.com

13:43

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c5 --- Comment #5 from Lukas Ocilka 2012-11-16 13:43:21 UTC --- OK, I can do that for 12.2 as well. -- 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.

bugzilla_noreply＠novell.com

14:08

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c6 --- Comment #6 from Joschi Brauchle 2012-11-16 14:08:47 UTC --- I have done a first test with the yast2-runlevel-2.21.4 package from the YaST:Head 12.2 repo, and that test was *not* successful... But I'll try again and report back. By the way, just to make sure: Have you considered, that the problem of services not starting without a reboot also affects *all services configured during in other autoyast modules*? That is, the problem is not limited to the services specified in the <runlevel> tag, but also affects "sssd" and "autofs" for example, which are configured during yast2-ldapclient... -- 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.

bugzilla_noreply＠novell.com

14:56

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c7 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #7 from Lukas Ocilka 2012-11-16 14:56:13 UTC --- (In reply to comment #6)

...

I have done a first test with the yast2-runlevel-2.21.4 package from the YaST:Head 12.2 repo, and that test was *not* successful... But I'll try again and report back.

I'll be unifying the solution with another one already provided in Runlevel Proposal during installation. That one also takes take of service dependencies. Solution that I've implemented for this bug only additionally takes into consideration the currently running runlevel. I will merge these two together.

...

By the way, just to make sure: Have you considered, that the problem of services not starting without a reboot also affects *all services configured during in other autoyast modules*?

No, that's not a problem or runlevel, I'm afraid, but I'll think about it and if there is a simple solution that will not break anything else (for instance the runlevel configuration on a running system) I might add it.

...

That is, the problem is not limited to the services specified in the <runlevel> tag, but also affects "sssd" and "autofs" for example, which are configured during yast2-ldapclient...

Then it seems that either yast2-ldap client should start these services or AutoYast should start all enabled services at the end of the run. -- 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.

bugzilla_noreply＠novell.com

14:57

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c8 --- Comment #8 from Lukas Ocilka 2012-11-16 14:57:25 UTC --- Hmm, next time I should read what I write before submitting :) -- 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.

bugzilla_noreply＠novell.com

15:41

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c9 --- Comment #9 from Joschi Brauchle 2012-11-16 15:41:20 UTC --- (In reply to comment #6)

...

I have done a first test with the yast2-runlevel-2.21.4 package from the YaST:Head 12.2 repo, and that test was *not* successful... But I'll try again and report back.

...

Then it seems that either yast2-ldap client should start these services or AutoYast should start all enabled services at the end of the run. Ok, sounds reasonable. I will open a separate bugreport for this. But, if AutoYast would add a function that starts all enabled services at the end of it's run, you would not have to include that functionality into the runlevel or any other module, right? Maybe finding an overall solution to this

I've done some more tests (and added debug output to RunlevelEd.ycp) and all tests failed to start the services, because the function GetCurrentRunlevel returns "unknown". Hence, the "if (contains(service_runlevels, GetCurrentRunlevel()))" never succeeds... (In reply to comment #7) problem would fix this particular problem in the runlevel module as well. -- 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.

bugzilla_noreply＠novell.com

3 Dec 3 Dec

12:15

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c10 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #10 from Lukas Ocilka 2012-12-03 12:15:22 UTC --- I've just submitted a new version to YaST::Head project https://build.opensuse.org/package/repositories?package=yast2-runlevel&project=YaST%3AHead yast2-runlevel-2.21.5 -- 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.

bugzilla_noreply＠novell.com

12:16

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c11 --- Comment #11 from Lukas Ocilka 2012-12-03 12:16:51 UTC --- There were a bit bigger changes and you can all see them here: https://github.com/yast/yast-runlevel/commit/1ebf0da6e24aaa63b6bc9bf45c37846... -- 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.

bugzilla_noreply＠novell.com

4 Dec 4 Dec

13:19

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c12 --- Comment #12 from Joschi Brauchle 2012-12-04 13:18:59 UTC --- I did a test-installation and all services are started! Actually, in my AutoYast scenario, this creates a problem :-( As regular <post-scripts> are run after Yast-modules are run, runlevel starts services which are not yet able to run in my installation. As an example: I use GSSAPI along with the SSSD service. But the YaST SSSD module is not able to configure GSSAPI correctly. Thus, I do this with a post-script. But now, Yast-runlevel starts SSSD before the post-script has run and thus SSSD fails to start because it is not correctly configured! Same with NFS and AutoFS for me... Looking at the AutoYast flowchart http://suse.gansert.net/wp-content/uploads/2011/08/autoyast_workflow.jpg I think it would be better to start configured all services at the very end of the installation procedure (3rd to last step: "init to configured <runlevel>"). -- 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.

bugzilla_noreply＠novell.com

15:04

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c13 Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #13 from Joschi Brauchle 2012-12-04 15:04:38 UTC --- There seems to be a problem with starting dependencies. I get this in y2log when trying to start the nfs service (which depends on rpcbind): ------------------- [YCP] RunlevelEd.ycp:591 Services to start: ["autofs", "nfs", "rpcbind", "sshd"] [YCP] RunlevelEd.ycp:548 Service dependencies for autofs are: ["boot.udev", "boot.rootfsck", "boot.localfs", "syslog", "network"] [YCP] RunlevelEd.ycp:548 Service dependencies for nfs are: ["boot.udev", "boot.rootfsck", "boot.localfs", "syslog", "network", "rpcbind"] [YCP] RunlevelEd.ycp:548 Service dependencies for rpcbind are: ["boot.udev", "boot.rootfsck", "boot.localfs", "syslog", "network"] [YCP] RunlevelEd.ycp:548 Service dependencies for sshd are: ["boot.udev", "boot.rootfsck", "boot.localfs", "network"] [bash] ShellCommand.cc(shellcommand):78 [bash] ShellCommand.cc(shellcommand):78 Note: This output shows SysV services only and does not include native [bash] ShellCommand.cc(shellcommand):78 systemd services. SysV configuration data might be overridden by native [bash] ShellCommand.cc(shellcommand):78 systemd configuration. [bash] ShellCommand.cc(shellcommand):78 [YCP] Service.ycp:321 Running service initscript autofs status [liby2util++] ExternalProgram.cc(start_program):202 Executing '/bin/sh' '-c' 'TERM=dumb /etc/init.d/autofs status' [liby2util++] ExternalProgram.cc(checkStatus):361 pid 14741 exited with status 3 [YCP] Service.ycp:356 Time spent: 20 msecs, retcode: 3 [agent-process] ProcessAgent.cc(Execute):521 Releasing Process object 14741... [YCP] Service.ycp:321 Running service initscript autofs start [liby2util++] ExternalProgram.cc(start_program):202 Executing '/bin/sh' '-c' 'TERM=dumb /etc/init.d/autofs start' [YCP] Service.ycp:356 Time spent: 2600 msecs, retcode: 0 [agent-process] ProcessAgent.cc(Execute):521 Releasing Process object 14746... [bash] ShellCommand.cc(shellcommand):78 [bash] ShellCommand.cc(shellcommand):78 Note: This output shows SysV services only and does not include native [bash] ShellCommand.cc(shellcommand):78 systemd services. SysV configuration data might be overridden by native [bash] ShellCommand.cc(shellcommand):78 systemd configuration. [bash] ShellCommand.cc(shellcommand):78 [YCP] Service.ycp:321 Running service initscript nfs status [liby2util++] ExternalProgram.cc(start_program):202 Executing '/bin/sh' '-c' 'TERM=dumb /etc/init.d/nfs status' [liby2util++] ExternalProgram.cc(checkStatus):361 pid 14780 exited with status 3 [YCP] Service.ycp:356 Time spent: 20 msecs, retcode: 3 [agent-process] ProcessAgent.cc(Execute):521 Releasing Process object 14780... [YCP] Service.ycp:321 Running service initscript nfs start [liby2util++] ExternalProgram.cc(start_program):202 Executing '/bin/sh' '-c' 'TERM=dumb /etc/init.d/nfs start' [liby2util++] ExternalProgram.cc(checkStatus):361 pid 14786 exited with status 3 [YCP] Service.ycp:356 Time spent: 20 msecs, retcode: 3 [agent-process] ProcessAgent.cc(Execute):521 Releasing Process object 14786... [YCP] RunlevelEd.ycp:661 Unable to start service nfs [YCP] Report.ycp:523 Cannot start 'nfs' service ------------------- Clearly, rpcbind is not started prior to nfs! -- 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.

bugzilla_noreply＠novell.com

15:19

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c14 --- Comment #14 from Joschi Brauchle 2012-12-04 15:19:17 UTC --- (In reply to comment #12)

...

Looking at the AutoYast flowchart http://suse.gansert.net/wp-content/uploads/2011/08/autoyast_workflow.jpg I think it would be better to start configured all services at the very end of the installation procedure (3rd to last step: "init to configured <runlevel>").

Also note that currently runlevel runs before the sysconfig module (and others). Hence, it may start services, where the sysconfig module has not had the change to make its changes! In my case, I use sysconfig to set some variables in /etc/sysconfig/autofs. But runlevel starts autofs before these variables are set! -- 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.

bugzilla_noreply＠novell.com

14 Dec 14 Dec

12:30

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c15 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |ASSIGNED --- Comment #15 from Lukas Ocilka 2012-12-14 12:30:24 UTC --- In that case there's really no other way than just not starting all the services manually but let AutoYast start all the services automatically as described at the end of comment #12 I'll remove starting the services from AutoYast functions in Runlevel. -- 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.

bugzilla_noreply＠novell.com

13:57

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c16 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |locilka@suse.com AssignedTo|locilka@suse.com |fehr@suse.com --- Comment #16 from Lukas Ocilka 2012-12-14 13:57:35 UTC --- Thomas, it seems that AutoYast needs to adjust all the systemd services at the end of its run. Runlevel module cannot do that because of nested dependencies. Runlevel can (and does) enable all the needed services but doesn't start them (yast2-runlevel-2.21.6) I suggest to initialize to the default runlevel at the end of Autoyast run. -- 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.

bugzilla_noreply＠novell.com

14:01

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c17 Lukas Ocilka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #17 from Lukas Ocilka 2012-12-14 14:01:09 UTC --- Frederic, what's the preferred solution to start all the services that are "enabled" but not running in the proper order? Is there a way using systemd/systemctl to do so? Can we, for instance, use something like `systemctl start default.target`? Is there a better way? -- 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.

bugzilla_noreply＠novell.com

14:11

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c18 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|fcrozat@suse.com | --- Comment #18 from Frederic Crozat 2012-12-14 14:11:27 UTC --- (In reply to comment #17)

...

Frederic, what's the preferred solution to start all the services that are "enabled" but not running in the proper order? Is there a way using systemd/systemctl to do so?

Can we, for instance, use something like `systemctl start default.target`? Is there a better way?

"systemctl isolate default.target" would do that, but be carefull, it would also stop all services which are not enabled in the specified target / service. -- 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.

bugzilla_noreply＠novell.com

3 Feb 3 Feb

13:11

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c19 --- Comment #19 from Joschi Brauchle 2013-02-03 13:11:20 UTC --- So with this problem still persists in 12.3 Beta1 and the very latest YaST-packages from OBS... How are chances this will be fixed in 12.3 Final? -- 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.

bugzilla_noreply＠novell.com

5 Feb 5 Feb

14:18

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c20 --- Comment #20 from Thomas Fehr 2013-02-05 14:18:40 UTC --- I seriously hope I will have time to have a closer look at this (and some other systemd related autoyast problems) this week or next week, which should be in time for 12.3 if the fix is not to hard to 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.

bugzilla_noreply＠novell.com

16:52

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c21 --- Comment #21 from Joschi Brauchle 2013-02-05 16:52:11 UTC --- Thank you, I really appreciate your efforts. I suspect that many of the reported AutoYast problems actually boil down to the same/similar cause... I have a minimal 12.3 AY XML ready for our setup that shows all these issues and I am happy to test patches, if help is needed! -- 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.

bugzilla_noreply＠novell.com

17:08

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c22 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |joschibrauchle@gmx.de --- Comment #22 from Thomas Fehr 2013-02-05 17:08:25 UTC --- Did you already attach this autoyas XML already somewhere? If no it could be helpful if you could attach it here -- 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.

bugzilla_noreply＠novell.com

6 Feb 6 Feb

16:04

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c23 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|joschibrauchle@gmx.de |fcrozat@suse.com --- Comment #23 from Thomas Fehr 2013-02-06 16:04:15 UTC --- I now added a call to "systemctl isolate default.target" after autoyast did its configuration step in second stage. Unfortunately this hangs (probably forever, I killed it after some minutes). Is there an alternative way to reach what we need with systemctl. Any way to debug why it hangs. If I kill systemctl call, yast in second stage finishes. When I then call "systemctl isolate default.target" on the command line it also hangs. If I reboot the system and call the same command it finishes after about 11 seconds. Any suggestions? -- 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.

bugzilla_noreply＠novell.com

16:09

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c24 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |fcrozat@suse.com InfoProvider|fcrozat@suse.com | --- Comment #24 from Frederic Crozat 2013-02-06 16:09:52 UTC --- try "systemctl --ignore-dependencies isolate default.target". If you have a minimal autoyast / appliance config somewhere to test, that would be helpful for me. -- 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.

bugzilla_noreply＠novell.com

16:14

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c25 --- Comment #25 from Thomas Fehr 2013-02-06 16:14:52 UTC --- Thanks, will give it a try. If it does not help, I will give you access to a system where the hang can be reproduced on the command line hopefully. Since after a reboot the hang does not occur any more, I would assume this is a special problem during second stage of install. -- 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.

bugzilla_noreply＠novell.com

17:00

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c26 --- Comment #26 from Thomas Fehr 2013-02-06 17:00:32 UTC --- Adding --ignore-dependencies did not prevent the hang. With some more fiddling around I would assume the problem is caused by the following: - after first reboot at end of first stage install there is a systemd service /usr/lib/systemd/system/YaST2-Second-Stage.service that calls YaST to do second stage install - now there is a call to "systemctl --ignore-dependencies isolate default.target" from while the YaST2-Second-Stage.service is still executing - as long as YaST2-Second-Stage.service is still running, calling "systemctl isolate default.target" hangs regardless of parameter --ignore-dependencies -- 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.

bugzilla_noreply＠novell.com

17:10

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c27 --- Comment #27 from Frederic Crozat 2013-02-06 17:10:28 UTC --- There was a bug in systemd (fixed in Factory) which wasn't respecting --ignore-dependencies, so you could be hit by this. To double-check, try to boot with "systemd.log_level=debug systemd.log_target=kmsg" and after the isolate call (with or without --ignore-dependencies", check dmesg output and attacht the log here, we will see what is happening at systemd level. -- 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.

bugzilla_noreply＠novell.com

17:49

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c28 --- Comment #28 from Thomas Fehr 2013-02-06 17:48:57 UTC --- Created an attachment (id=523606) --> (http://bugzilla.novell.com/attachment.cgi?id=523606) dmesg output with systemd debug on -- 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.

bugzilla_noreply＠novell.com

17:50

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c29 --- Comment #29 from Thomas Fehr 2013-02-06 17:50:10 UTC --- systemd version on 12.3 Beta1 is systemd-195-11.1.i586 I attached the debug file created after the command systemctl --ignore-dependencies isolate default.target debug of the systemctl command started at 254.760987 If you would like to have a look at the system yourself, it is f134.suse.de, root password is "rootpw", ssh access is on. It is still in a state where systemctl --ignore-dependencies isolate default.target hangs -- 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.

bugzilla_noreply＠novell.com

17:51

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |fcrozat@suse.com -- 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.

bugzilla_noreply＠novell.com

7 Feb 7 Feb

17:55

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c30 --- Comment #30 from Thomas Fehr 2013-02-07 17:55:18 UTC --- Just for information: The same hang as in Beta#1 also occurs in RC1 of 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.

bugzilla_noreply＠novell.com

11 Feb 11 Feb

15:45

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c31 --- Comment #31 from Thomas Fehr 2013-02-11 15:45:21 UTC --- Frederic did you already have to to look into attachment in comment#28 -- 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.

bugzilla_noreply＠novell.com

15:50

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c32 --- Comment #32 from Frederic Crozat 2013-02-11 15:50:26 UTC --- (In reply to comment #31)

...

Frederic did you already have to to look into attachment in comment#28

no sorry, been busy with other urgent things right now, I'll try later this week. -- 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.

bugzilla_noreply＠novell.com

14 Feb 14 Feb

12:56

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c33 --- Comment #33 from Thomas Fehr 2013-02-14 12:56:26 UTC --- Ok I did some more investigations yesterday. The call to "systemctl definitely hangs forever when called by yast in second installation stage. This is because second install stage itself is started by the systemd service "YaST2-Second-Stage.service" this service would be finished when yast finishes. Since yast wait for "systemctl --ignore-dependencies isolate default.target" it in turn never finish --> classic deadlock. list of jobs from system during the deadlock: f134:~ # systemctl --full list-jobs JOB UNIT TYPE STATE 84 systemd-update-utmp-runlevel.service start waiting 1 graphical.target start waiting 2 multi-user.target start waiting 76 getty.target start waiting 77 getty@tty1.service start waiting 92 systemd-readahead-done.timer start waiting 90 YaST2-Firstboot.service start waiting 93 YaST2-Second-Stage.service start running 56 SuSEfirewall2_init.service start waiting 226 SuSEfirewall2.service start waiting I tried the following stuff to work around that: 1) call "systemctl disable YaST2-Second-Stage.service" before call to "isolate" --> does not help, job for YaST2-Second-Stage.service is already in jobs queue disabling it does not remove it from this queue 2) call "systemctl cancel 93" with 93 being the job id of YaST2-Second-Stage.service this makes systemctl isolate call finish. Unfortunately something is killing yast right away when I do this. I assume this killing is done by systemd. Any idea how to solve that? -- 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.

bugzilla_noreply＠novell.com

16:18

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c34 --- Comment #34 from Thomas Fehr 2013-02-14 16:18:09 UTC --- Some more testing showed that the call to "systemctl cancel " make systemd kill yast. Since yast would call "systemctl --ignore-dependencies isolate default.target" after call to "systemctl cancel ..." it is a race if yast is fast enough to issue the call to "systemctl isolate .." before it gets killed. We definitely need a way to prevent systemd from killing yast under these circumstances. -- 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.

bugzilla_noreply＠novell.com

16:33

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c35 --- Comment #35 from Joschi Brauchle 2013-02-14 16:33:13 UTC --- Just asking with my limited understanding of what is happening: Why must YaST wait for "systemctl isolate .." to finish? Could it not just issue that call and then quit somehow, thus breaking the 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.

bugzilla_noreply＠novell.com

16:39

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c36 --- Comment #36 from Joschi Brauchle 2013-02-14 16:39:09 UTC ---

...

From the manpage of systemctl, there is: "--no-block Do not synchronously wait for the requested operation to finish. If this is not specified the job will be verified, enqueued and systemctl will wait until it is completed. By passing this argument it is only verified and enqueued."

So maybe "systemctl --no-block --ignore-dependencies isolate default.target" would add this call to the queue and then YaST could continue cleaning up...? -- 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.

bugzilla_noreply＠novell.com

17:15

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c37 --- Comment #37 from Thomas Fehr 2013-02-14 17:15:13 UTC --- My expectation would be: If autoyast finishes at this stage, all services configured in default.target are available. Autoyast init scripts should have the above guarantee that at the time of their execution all services are up and running. If this is not the case init scripts have to start/stop system service (like is the case in your bnc#803577) which I think should not be necessary and potentially causes new problems. If autoyast does not wait for "systemctl isolate .." to really finish, the state in which autoyast init scripts are executed is not well defined since if some service need a longer initialization time it could be possible that it is not (yet) initialized at the time the autoyast init scripts are executed. -- 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.

bugzilla_noreply＠novell.com

17:21

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c38 --- Comment #38 from Frederic Crozat 2013-02-14 17:21:28 UTC --- (In reply to comment #37)

...

My expectation would be: If autoyast finishes at this stage, all services configured in default.target are available.

Autoyast init scripts should have the above guarantee that at the time of their execution all services are up and running. If this is not the case init scripts have to start/stop system service (like is the case in your bnc#803577) which I think should not be necessary and potentially causes new problems.

In that case, the service for starting autoyast scripts should have : After=default.target This will ensure it is started "after" all the services started for default "runlevel". -- 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.

bugzilla_noreply＠novell.com

17:29

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c Joschi Brauchle changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |803577 -- 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.

bugzilla_noreply＠novell.com

17:39

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c39 --- Comment #39 from Joschi Brauchle 2013-02-14 17:39:18 UTC --- (In reply to comment #38)

...

In that case, the service for starting autoyast scripts should have : After=default.target

This will ensure it is started "after" all the services started for default "runlevel".

That make sence, but then again, "isolate default.target" will end all services not part of the default target, right? So I would image systemd to end/cancel the autoyast init scripts if they are not wanted by the default target. Hence, autoyast init scripts must be wanted by **and** started after the default target..? Is that possible..? -- 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.

bugzilla_noreply＠novell.com

17:46

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c40 --- Comment #40 from Thomas Fehr 2013-02-14 17:46:12 UTC --- My thinking about this was along the same lines. Currently it has "WantedBy=default.target" I would be surprised if it could have "After=default.target" at the same time. Will try with this some more next week. -- 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.

bugzilla_noreply＠novell.com

17:54

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c41 --- Comment #41 from Frederic Crozat 2013-02-14 17:54:46 UTC --- Another potential solution would be to use "Type=idle" (only available in 12.3 and later) -- 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.

bugzilla_noreply＠novell.com

17:59

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c42 --- Comment #42 from Joschi Brauchle 2013-02-14 17:59:45 UTC --- Maybe it works by replacing "WantedBy=default.target" with "After=default.target" and then issuing: systemctl --no-block isolate default.target systemctl --no-block start autoyast-initscripts.service and then finishing up within YaST stage2. I would image systemd to order them and start them correctly, once YaST-stage2 finishes? BTW, just asking: is the "--ignore-dependencies" currently used with "isolate default.target" really needed? -- 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.

bugzilla_noreply＠novell.com

18:04

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c43 --- Comment #43 from Frederic Crozat 2013-02-14 18:04:24 UTC --- (In reply to comment #42)

...

BTW, just asking: is the "--ignore-dependencies" currently used with "isolate default.target" really needed?

No, I'm not sure it is needed.. -- 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.

bugzilla_noreply＠novell.com

18:09

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c44 --- Comment #44 from Thomas Fehr 2013-02-14 18:09:51 UTC --- (In reply to comment #42)

...

Maybe it works by replacing "WantedBy=default.target" with "After=default.target" and then issuing: systemctl --no-block isolate default.target systemctl --no-block start autoyast-initscripts.service and then finishing up within YaST stage2.

I would image systemd to order them and start them correctly, once YaST-stage2 finishes?

BTW, just asking: is the "--ignore-dependencies" currently used with "isolate default.target" really needed?

But what if for some reason "systemctl isolate " hangs (potentially forever) for some reason. YaST is finished, user expects system to be usable but autoyast-initscripts.service is delayed forever. Currently there is a log entry on autoyast screen saying Activating systemd default target So if it hangs it is quite clear, something is wrong and where to look. This information would be much harder to get when using "--no-block". -- 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.

bugzilla_noreply＠novell.com

18 Feb 18 Feb

12:29

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c45 --- Comment #45 from Frederic Crozat 2013-02-18 12:29:48 UTC --- Do you have a autoyast example I could use to replicate the issue locally and investigate ? It might be faster than going back and forth with bugzilla :) -- 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.

bugzilla_noreply＠novell.com

13:01

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c46 --- Comment #46 from Thomas Fehr 2013-02-18 13:01:08 UTC --- Current state is the following: - autoyast2 wants to initiate current runlevel by calling "systemctl isolate default-target" - since yast2 itself is started by a systemd service (YaST2-Second-Stage.service) calling "systemctl isolate default-target" blocks forever - so far I do not want to simply use "--no-block" since when autoyast2 finishes (and autoyast init scripts are called afterwards) I wnt to be sure that all services started with "systemctl isolate default-target" are up and running This can be reproduced not only with autoyast but with every yast2 installation while yast is running from YaST2-Second-Stage.service after first reboot. A call to "systemctl isolate default-target" hangs until yast is finished in second stage. So if called from inside yast there is a deadlock (yast2 waits for systemctl call to finish, systemctl call waits for yast to finish). What I now plan to implement: - call "systemctl isolate" with "--no-block" option - afterwards call "systemctl list-jobs" repeatedly to determine when the only service not yet finished is YaST2-Second-Stage.service itself. - continue within autoyast2 This should reach both goals: - the deadlock is broken since systemctl with "--no-block" should return immediately - nevertheless all services should be up and running when autoyast finishes since autoyast waited until "systemctl list-jobs" shows no more running jobs -- 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.

bugzilla_noreply＠novell.com

13:37

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c47 Frederic Crozat changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED InfoProvider|fcrozat@suse.com | --- Comment #47 from Frederic Crozat 2013-02-18 13:37:31 UTC --- (In reply to comment #46)

...

Current state is the following: - autoyast2 wants to initiate current runlevel by calling "systemctl isolate default-target" - since yast2 itself is started by a systemd service (YaST2-Second-Stage.service) calling "systemctl isolate default-target" blocks forever - so far I do not want to simply use "--no-block" since when autoyast2 finishes (and autoyast init scripts are called afterwards) I wnt to be sure that all services started with "systemctl isolate default-target" are up and running

Why is this call needed at all in the first place ? systemd has been initially started to go to this target, so it will go there, after YaST2 Second Stage is finished. I'm a bit lost (and confused on when Second Stage is being expected to started, which seems different in your case and the usual case). -- 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.

bugzilla_noreply＠novell.com

14:13

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c48 --- Comment #48 from Thomas Fehr 2013-02-18 14:13:36 UTC --- It was you who suggested that call in comment#18... In autoyast second stage additional rpms are installed. Services are enabled or disabled, configuration could be changed, so it is necessary to make sure that when autoyast finishes, services are up and running since the autoyast init scripts (which are excuted after autoyast is finished) could rely on the services being available. YaST Second stage is started exactly the same time regardless of interactive or autoyast installation. -- 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.

bugzilla_noreply＠novell.com

19 Feb 19 Feb

10:47

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c49 Thomas Fehr changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #49 from Thomas Fehr 2013-02-19 10:47:18 UTC --- I would assume that the change to explicitly call "systemctl isolate" after second stage package installation and configuration should fix this problem. So please test with autoyast package version 2.23.4 (will probably be part or openSuSE 12.3 RC2) and reopen if there are still problems. -- 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.

bugzilla_noreply＠novell.com

12:00

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c50 --- Comment #50 from Bernhard Wiedemann 2013-02-19 13:00:19 CET --- This is an autogenerated message for OBS integration: This bug (769924) was mentioned in https://build.opensuse.org/request/show/155804 Factory / autoyast2 -- 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.

bugzilla_noreply＠novell.com

13:46

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c51 --- Comment #51 from Joschi Brauchle 2013-02-19 13:46:51 UTC --- I can confirm that after a test installation, all services included in our AutoYast profile are in correct state! Only exception is that network.service is not running, but I think this is a separate problem with current openSUSE12.3 RC1... -- 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.

bugzilla_noreply＠novell.com

13:54

New subject: [Bug 769924] the autoyast runlevel config kicks in after reboot only with systemd

https://bugzilla.novell.com/show_bug.cgi?id=769924 https://bugzilla.novell.com/show_bug.cgi?id=769924#c52 --- Comment #52 from Frederic Crozat 2013-02-19 13:54:25 UTC --- excellent news ! -- 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.

4090

Age (days ago)

4320

Last active (days ago)

List overview

Download

54 comments

1 participants

participants (1)

bugzilla_noreply＠novell.com

[Bug 769924] New: the autoyast runlevel config kicks in after reboot only with systemd

tags

participants (1)