[Bug 812630] New: yast crashes on updates during installation
https://bugzilla.novell.com/show_bug.cgi?id=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c0 Summary: yast crashes on updates during installation Classification: openSUSE Product: openSUSE 12.3 Version: Final Platform: x86-64 OS/Version: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mike.catanzaro@gmail.com QAContact: jsrain@suse.com Found By: --- Blocker: --- Created an attachment (id=532742) --> (http://bugzilla.novell.com/attachment.cgi?id=532742) y2logs User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0 I was installing openSUSE 12.3 (GNOME desktop) from the DVD. I unchecked "automatic configuration" at the beginning and so I had the opportunity to do a system update at the end of the installation. During the update, yast died; I wound up on a tty that said something along the lines of "yast caught signal 15" (I believe that was the number) and then "yast caught signal 1". I powered off my computer manually; when I powered on I was allowed to complete the installation but chose to skip updates this time. I did NOT lose any data; YaST remembered all of my settings and most of the updates had been applied. So +1 for graceful failure, at least. Reproducible: Didn't try y2logs attached! -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c Xiaolong Li <xlli@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xlli@suse.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.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.
https://bugzilla.novell.com/show_bug.cgi?id=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c1 Thomas Fehr <fehr@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |jsuchome@suse.com --- Comment #1 from Thomas Fehr <fehr@suse.com> 2013-04-02 09:06:11 UTC --- crash occured in /usr/share/YaST2/clients/online_update_install.yc reassigned to maintainer of yast2-online-update -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c2 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |lslezak@suse.com --- Comment #2 from Jiří Suchomel <jsuchome@suse.com> 2013-04-02 14:24:07 UTC --- (In reply to comment #1)
crash occured in /usr/share/YaST2/clients/online_update_install.yc reassigned to maintainer of yast2-online-update
It's actually PkgCommit call that was done from that ycp code. Ladislav, any idea what went wrong? -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c3 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwayson@gmail.com --- Comment #3 from Jiří Suchomel <jsuchome@suse.com> 2013-04-02 14:57:02 UTC --- *** Bug 812479 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=812479 -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c4 Ladislav Slezak <lslezak@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW CC| |lslezak@suse.com InfoProvider|lslezak@suse.com | --- Comment #4 from Ladislav Slezak <lslezak@suse.com> 2013-04-02 15:09:25 UTC --- signal: YaST got signal 15 at YCP file /usr/share/YaST2/clients/online_update_install.ycp:91 ylog: 2013-03-31 22:24:41 <1> linux-87mu.site(2122) [zypp++] ExternalProgram.cc(start_program):229 Executing 'rpm' '--root' '/' '--dbpath' '/var/lib/rpm' '-U' '--percent' '--force' '--nodeps' '--' '/var/cache/zypp/packages/repo-update/noarch/yast2-installation-2.23.13-1.4.3.noarch.rpm' 2013-03-31 22:24:41 <1> linux-87mu.site(2122) [zypp++] ExternalProgram.cc(start_program):381 pid 15581 launched 2013-03-31 22:24:42 <2> linux-87mu.site(2122) [Gdk] yast2-gtk:0 y2base: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. 2013-03-31 22:24:42 <2> linux-87mu.site(2122) [Gdk] yast2-gtk:0 So it happens when installing yast2-installation update. Command "rpm -q --scripts yast2-installation" prints quite a lot of RPM scripts related to YaST2-Second-Stage.service YaST2-Firstboot.service systemd files. And AFAIK the problem has not been reported for installed system I guess the problem is in the scripts which are executed when the second stage is running, so it is probably somehow related to changes in YaST2-Second-Stage.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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c5 --- Comment #5 from Ladislav Slezak <lslezak@suse.com> 2013-04-02 15:12:03 UTC --- I guess Yast is killed by systemd when updating the files. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c6 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #6 from Jiří Suchomel <jsuchome@suse.com> 2013-04-02 15:12:51 UTC --- (In reply to comment #4)
And AFAIK the problem has not been reported for installed system I guess the problem is in the scripts which are executed when the second stage is running, so it is probably somehow related to changes in YaST2-Second-Stage.service file.
... additionally, we've not met this before since we didn't release update for yast2-installation until now. Frederic, seems like those RPM scripts in yast2-installation are wrong... ? -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c7 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fcrozat@suse.com InfoProvider|fcrozat@suse.com |jsuchome@suse.com --- Comment #7 from Frederic Crozat <fcrozat@suse.com> 2013-04-02 15:34:58 UTC --- Hmm, the systemd macros are running "/usr/bin/systemctl try-restart YaST2-Second-Stage.service YaST2-Firstboot.service" on upgrade, which is causing the issue. Is YaST setting a specific environment variable during the upgrade ? I just noticed we had if test "$YAST_IS_RUNNING" != "instsys" -a "$DISABLE_RESTART_ON_UPDATE" != yes ; then \ in %restart_on_update macro but this wasn't part of systemd macros (I can push that as an update on systemd but yast2-installation will need to be rebuild with the fixed macros). -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c8 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|jsuchome@suse.com |fcrozat@suse.com --- Comment #8 from Jiří Suchomel <jsuchome@suse.com> 2013-04-02 15:43:06 UTC --- (In reply to comment #7)
Hmm, the systemd macros are running "/usr/bin/systemctl try-restart YaST2-Second-Stage.service YaST2-Firstboot.service" on upgrade, which is causing the issue.
Is YaST setting a specific environment variable during the upgrade ?
I'm not aware of any other than YAST_IS_RUNNING. Is there a way to adapt systemd macros during 2nd stage, so I can test if it will help? I'm able to reproduce the situation described in bug, so if I could patch/restart something right before YaST starts online update, that would be nice. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c9 --- Comment #9 from Ladislav Slezak <lslezak@suse.com> 2013-04-02 16:01:40 UTC --- (In reply to comment #7)
Is YaST setting a specific environment variable during the upgrade ?
Unfortunately not, it sets only YAST_IS_RUNNING to "instsys" in the first stage, in the second stage it is "yes" which is the same as in installed system. (https://github.com/yast/yast-core/blob/master/liby2/src/genericfrontend.cc#L...) But maybe you could check for running yast via pgrep or something like that... (I use it in webyast like this: https://github.com/webyast/webyast/blob/master/plugins/status/app/models/met...) -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c10 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #10 from Frederic Crozat <fcrozat@suse.com> 2013-04-02 16:03:17 UTC --- (In reply to comment #8)
(In reply to comment #7)
Hmm, the systemd macros are running "/usr/bin/systemctl try-restart YaST2-Second-Stage.service YaST2-Firstboot.service" on upgrade, which is causing the issue.
Is YaST setting a specific environment variable during the upgrade ?
I'm not aware of any other than YAST_IS_RUNNING.
Is there a way to adapt systemd macros during 2nd stage, so I can test if it will help?
Arggg, it is in %service_del_postun, so the 'try-restart' call is in the "old" package being uninstalled, not the "new" one being upgraded.. I don't think we can prevent the %postun in the old package of being 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.
https://bugzilla.novell.com/show_bug.cgi?id=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c11 --- Comment #11 from Frederic Crozat <fcrozat@suse.com> 2013-04-02 16:18:26 UTC --- (In reply to comment #10)
Arggg, it is in %service_del_postun, so the 'try-restart' call is in the "old" package being uninstalled, not the "new" one being upgraded..
I don't think we can prevent the %postun in the old package of being run :(
After searching a little more in systemd, we could add either RefuseManualStart=true or RefuseManualStop=true in Yast second-stage systemd unit file. This should make the try-restart do nothing. I didn't test it, though.. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c12 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #12 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 06:14:26 UTC --- (In reply to comment #11)
After searching a little more in systemd, we could add either RefuseManualStart=true or RefuseManualStop=true in Yast second-stage systemd unit file. This should make the try-restart do nothing.
But that file is still part of yast2-installation, right? So we could not update it before the old one is used... -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c13 --- Comment #13 from Ladislav Slezak <lslezak@suse.com> 2013-04-03 08:26:07 UTC --- Well, it depends how systemd handles service files, if try-restart call loads the updated config it could help... Jiri, could you try it? -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c14 --- Comment #14 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 08:35:08 UTC --- I tried to put RefuseManualStop=true into YaST2-Second-Stage.service before online update run and it did not help. (In reply to comment #13)
Well, it depends how systemd handles service files, if try-restart call loads the updated config it could help...
The problem is, how could we deliver corrected service file without reinstalling yast2-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.
https://bugzilla.novell.com/show_bug.cgi?id=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c15 --- Comment #15 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 08:37:03 UTC --- One idea: we could try to create patch that contains just some scripts fixing our current situation (sed for systemd files or something like that). If we'd mark such patch as 'yast restart needed' that it would be installed before any other later patch, YaST would even be forced to restart before installing the rest of patches. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c16 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #16 from Frederic Crozat <fcrozat@suse.com> 2013-04-03 09:33:18 UTC --- Be sure to put: RefuseManualStart=true in the [Unit] section of yast2 second stage (and not in [Service]). I've double-checked how files and %postun are handled when upgrading a package and the "new" files are in place before %postun of the old package is run. And we run "reload" on %post of the new package, so everything should be fine in the ordering.. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c17 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #17 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 10:04:38 UTC --- (In reply to comment #16)
Be sure to put: RefuseManualStart=true in the [Unit] section of yast2 second stage (and not in [Service]).
That's what I did with YaST2-Second-Stage.service and it did not seem to help. Should I reload/restart something after the editing? Latest log lines from /var/log/messages: 2013-04-02T16:38:46.812222+02:00 linux systemd[1]: Reloading. 2013-04-02T16:38:50.746452+02:00 linux systemd[1]: Reloading. 2013-04-02T16:38:50.926531+02:00 linux systemd[1]: Stopping YaST2 Second Stage... Would it help to add some more debugging? -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c18 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #18 from Frederic Crozat <fcrozat@suse.com> 2013-04-03 10:10:06 UTC --- (In reply to comment #17)
(In reply to comment #16)
Be sure to put: RefuseManualStart=true in the [Unit] section of yast2 second stage (and not in [Service]).
That's what I did with YaST2-Second-Stage.service and it did not seem to help. Should I reload/restart something after the editing?
Yes, you need to run systemctl daemon-reload (this should be done by the current systemd macros). This should make try-restart to fail.
Latest log lines from /var/log/messages:
2013-04-02T16:38:46.812222+02:00 linux systemd[1]: Reloading. 2013-04-02T16:38:50.746452+02:00 linux systemd[1]: Reloading. 2013-04-02T16:38:50.926531+02:00 linux systemd[1]: Stopping YaST2 Second Stage...
Would it help to add some more debugging?
you can try to boot with systemd.log_level=debug but I don't think you'll get more info. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c19 --- Comment #19 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 10:46:13 UTC --- (In reply to comment #18)
(In reply to comment #17)
(In reply to comment #16)
Be sure to put: RefuseManualStart=true in the [Unit] section of yast2 second stage (and not in [Service]).
That's what I did with YaST2-Second-Stage.service and it did not seem to help. Should I reload/restart something after the editing?
Yes, you need to run systemctl daemon-reload (this should be done by the current systemd macros).
This should make try-restart to fail.
This did not help either. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c20 --- Comment #20 from Frederic Crozat <fcrozat@suse.com> 2013-04-03 12:29:57 UTC --- (In reply to comment #19)
(In reply to comment #18)
(In reply to comment #17)
(In reply to comment #16)
Be sure to put: RefuseManualStart=true in the [Unit] section of yast2 second stage (and not in [Service]).
That's what I did with YaST2-Second-Stage.service and it did not seem to help. Should I reload/restart something after the editing?
Yes, you need to run systemctl daemon-reload (this should be done by the current systemd macros).
This should make try-restart to fail.
This did not help either.
Are you sure ? I've tested with another package which uses %service_* macros, adding RefuseManualStart=true to .service [Unit] and the service wasn't restarted after upgrading the package (I checked the service status before and after the upgrade). -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c21 --- Comment #21 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 12:51:13 UTC --- # cat /usr/lib/systemd/system/YaST2-Second-Stage.service [Unit] Description=YaST2 Second Stage After=apparmor.service local-fs.target plymouth-start.service Before=getty@tty1.service xdm.service network.service NetworkManager.service SuSEfirewall2_init.service SuSEfirewall2.service ConditionPathExists=/var/lib/YaST2/runme_at_boot RefuseManualStart=true ... linux-h0ye:~ # systemctl daemon-reload linux-h0ye:~ # systemctl status YaST2-Second-Stage YaST2-Second-Stage.service - YaST2 Second Stage Loaded: loaded (/usr/lib/systemd/system/YaST2-Second-Stage.service; enabled) Active: activating (start) since Tue, 2013-04-02 16:21:15 CEST; 14min ago Main PID: 359 (YaST2.Second-St) CGroup: name=systemd:/system/YaST2-Second-Stage.service ├ 359 /bin/sh /usr/lib/YaST2/startup/YaST2.Second-Stage ├ 1424 bash ├ 1496 /bin/sh /usr/lib/YaST2/startup/YaST2.call installation continue ├ 1956 Xorg -noreset -br -deferglyphs 16 vt07 ├ 1963 icewm -c preferences.yast2 -t yast2 ├ 2019 y2base installation ("continue") qt --noborder --auto-fonts --fullscreen ├ 2169 /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_udev_persistent ├ 2614 /bin/bash /usr/lib/YaST2/servers_non_y2/ag_initscripts └ 4554 /usr/bin/perl -w /usr/lib/YaST2/servers_non_y2/ag_netd Apr 02 16:21:15 linux.site systemd[1]: Starting YaST2 Second Stage... Apr 02 16:26:01 linux-h0ye postfix/postfix-script[2524]: fatal: the Postfix mail system is not running Apr 02 16:26:24 linux-h0ye postfix/postfix-script[4335]: refreshing the Postfix mail system Apr 02 16:26:55 linux-h0ye logger[5103]: BEGIN OF YAST2 INTERNET TEST Apr 02 16:27:10 linux-h0ye logger[5251]: END OF YAST2 INTERNET TEST After YaST crash: linux-h0ye:~ # systemctl status YaST2-Second-Stage YaST2-Second-Stage.service - YaST2 Second Stage Loaded: loaded (/usr/lib/systemd/system/YaST2-Second-Stage.service; enabled) Active: deactivating (final-sigterm) Main PID: 359 (code=killed, signal=TERM) CGroup: name=systemd:/system/YaST2-Second-Stage.service └ 1424 bash Apr 02 16:21:15 linux.site systemd[1]: Starting YaST2 Second Stage... Apr 02 16:26:01 linux-h0ye postfix/postfix-script[2524]: fatal: the Postfix mail system is not running Apr 02 16:26:24 linux-h0ye postfix/postfix-script[4335]: refreshing the Postfix mail system Apr 02 16:26:55 linux-h0ye logger[5103]: BEGIN OF YAST2 INTERNET TEST Apr 02 16:27:10 linux-h0ye logger[5251]: END OF YAST2 INTERNET TEST Apr 02 16:40:38 linux-h0ye os-prober[3551]: debug: /dev/sda1: is active swap Apr 02 16:41:49 linux-h0ye os-prober[8045]: debug: /dev/sda1: is active swap Apr 02 16:42:01 linux-h0ye systemd[1]: Stopping YaST2 Second Stage... -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c22 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #22 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 12:51:52 UTC --- Not sure if this can help, but to me it seems I did what I should... -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c23 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #23 from Frederic Crozat <fcrozat@suse.com> 2013-04-03 13:00:31 UTC --- Could you do the same test with systemd.log_level=debug (or send SIGRTMIN+22 to PID 1) ? I'm wondering if the issue is caused by the service being in "activating" state or it is just before YaST doesn't like to have the ground moved under its feet. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c24 --- Comment #24 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 14:19:33 UTC --- Created an attachment (id=533291) --> (http://bugzilla.novell.com/attachment.cgi?id=533291) /var/log/messages /var/log/messages after YaST was killed, with systemd verbose debugging -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c25 --- Comment #25 from Bill Wayson <bwayson@gmail.com> 2013-04-03 15:43:13 UTC --- Jiri, Frederic, Ladislav, You all appear to have a good handle on the issue and ideas of how to fix it. In the small chance you are interested, I ended my 12.3 installation at the point that yast2-installation crashes. When I resume it, the installation will pick up from the 'enter the host name' dialog and proceed to the network test and updating. Also, the openSUSE installation on this PC, which triple-boots Windows and Ubuntu 12.04, is just for learning and is not production, so I am willing to modify things on it or start a fresh installation. If you might want to take advantage of this, let me know and I will sit tight until contacted. Otherwise, I will resume my installation and first try to force yast2-installation to update, and then just skip updates if that fails. Thank you all for your great work. I am quite impressed with 12.3 after two earlier installations on notebooks, one of which is very underpowered. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c26 --- Comment #26 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 15:52:02 UTC --- Bill: seems like we've found the issue and also the way for fixing it, so there's no need to use your setup, thanks. Until the new fix is ready, I reccomend to skip running Online Update during installation. Installing patches later works fine. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c27 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |fcrozat@suse.com --- Comment #27 from Jiří Suchomel <jsuchome@suse.com> 2013-04-03 15:54:41 UTC --- Frederic: preparing new yast2-installation with modified YaST2-Second-Stage.service and offering this one to online update really helps. I assume this is gonna be our 12.3 solution. What about Factory, do you have something better? -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c28 Frederic Crozat <fcrozat@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW InfoProvider|fcrozat@suse.com | --- Comment #28 from Frederic Crozat <fcrozat@suse.com> 2013-04-03 16:04:59 UTC --- (In reply to comment #27)
Frederic: preparing new yast2-installation with modified YaST2-Second-Stage.service and offering this one to online update really helps.
I assume this is gonna be our 12.3 solution. What about Factory, do you have something better?
For Factory, I'll modify the systemd rpm macros to allow packages to not restart a service on upgrade (similar to what we have with the old %restart_on_upgrade macro). Therefore, I suggest to not commit RefuseManualStart=true in yast master branch but only in 12.3 branch. -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c29 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO InfoProvider| |maintenance@opensuse.org --- Comment #29 from Jiří Suchomel <jsuchome@suse.com> 2013-04-04 08:18:56 UTC --- Maintenance: could I proceed with new yast2-installation package? -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c30 Marcus Meissner <meissner@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED CC| |meissner@suse.com InfoProvider|maintenance@opensuse.org | --- Comment #30 from Marcus Meissner <meissner@suse.com> 2013-04-08 15:09:34 UTC --- please submit -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c31 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #31 from Jiří Suchomel <jsuchome@suse.com> 2013-04-09 08:14:49 UTC ---
osc maintenancerequest home:jsuchome:12.3 yast2-installation openSUSE:12.3 Using target project 'openSUSE:Maintenance' 163381
-- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c32 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |llunak@suse.com CC| |bnacht@web.de --- Comment #32 from Jiří Suchomel <jsuchome@suse.com> 2013-04-17 08:37:30 UTC --- *** Bug 813187 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=813187 --- Comment #33 from Jiří Suchomel <jsuchome@suse.com> 2013-04-17 08:37:31 UTC --- *** Bug 815169 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=815169 -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c32 Jiří Suchomel <jsuchome@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |llunak@suse.com CC| |bnacht@web.de --- Comment #32 from Jiří Suchomel <jsuchome@suse.com> 2013-04-17 08:37:30 UTC --- *** Bug 813187 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=813187 --- Comment #33 from Jiří Suchomel <jsuchome@suse.com> 2013-04-17 08:37:31 UTC --- *** Bug 815169 has been marked as a duplicate of this bug. *** http://bugzilla.novell.com/show_bug.cgi?id=815169 -- 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=812630 https://bugzilla.novell.com/show_bug.cgi?id=812630#c34 --- Comment #34 from Swamp Workflow Management <swamp@suse.de> 2013-04-17 15:05:28 UTC --- openSUSE-RU-2013:0693-1: An update that has one recommended fix can now be installed. Category: recommended (moderate) Bug References: 812630 CVE References: Sources used: openSUSE 12.3 (src): yast2-installation-2.23.14-1.8.6, yast2-installation-2.23.14-1.8.7 -- 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