[Bug 226036] New: Your handling of upgrading to kernel 2.6.18.2-33 causes confusion
https://bugzilla.novell.com/show_bug.cgi?id=226036 Summary: Your handling of upgrading to kernel 2.6.18.2-33 causes confusion Product: openSUSE 10.2 Version: RC 1 Platform: 32bit OS/Version: Linux Status: NEW Severity: Minor Priority: P5 - None Component: Kernel AssignedTo: kernel-maintainers@forge.provo.novell.com ReportedBy: kern@sibbald.com QAContact: qa@suse.de During a system update, kernel 2.6.18.2-33 was installed. On the positive side, there was a message that warned me to reboot. However, on the negative side: 1. There was no explicit reboot scheduled, so by the time everything was installed, I forgot to reboot. 2. Not rebooting caused autofs to fail because the .dep file for the old kernel was apparently wiped out. This caused me to thrash around a lot until I figured out the problem (autofs failed to start but messages indicated that it started correctly -- maybe another bug report). 3. Apparently the new kernel was not installed in the standard SuSE way as it was not the default -- I had to explicitly choose it from the boot menu. Suggestions: 1. Ask the user if he wants to reboot after everything is installed. 2. Avoid automatically installing kernels if they are going to blow away a previous installation. 3. I don't particularly like the OpenSuSE way of displaying the menu for kernels (It may be nice for dummies, but I would rather see all kernels listed and have the last one installed indicated as the default). That said, given the current way you do things, I think it would be better to install any new kernel as the current one. It is more consistent with how you have upgraded kernels in the past. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |bnc-team-screening@forge.provo.novell.com |maintainers@forge.provo.nove| |ll.com | Component|Kernel |YaST2 QAContact|qa@suse.de |jsrain@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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 mhorvath@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kernel-maintainers@forge.provo.novell.com |screening@forge.provo.novell| |.com | ------- Comment #2 from mhorvath@novell.com 2006-12-06 03:54 MST ------- Please don't write more than one problem into a one bug report. The issue about rebooting is resolved as invalid because you were suggested to reboot, you just probably missed it (according to the maintainers). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 ------- Comment #3 from kern@sibbald.com 2006-12-06 04:56 MST ------- Concerning multiple bugs: OK Concerning the invlid reboot request: no, I did not miss the message as I indicated in the bug report. The problem is, IMO, the message was given at an inappropriate time. It help the user if the message were printed or repeated at the end of the new package installation. As it was displayed before the installation started, there was a period of several hours before the reboot was possible, and with all the CD changes and other problems, such a request is easy to overlook. My suggestion was made to help you reduce your support requests. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 gregkh@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kernel- |bnc-team-screening@forge.provo.novell.com |maintainers@forge.provo.nove| |ll.com | ------- Comment #4 from gregkh@novell.com 2006-12-14 12:39 MST ------- Nothing the kernel group can do about this, reassigning... -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |yast2-maintainers@suse.de |screening@forge.provo.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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 ------- Comment #6 from kern@sibbald.com 2006-12-15 09:53 MST ------- Yes, this is probably a Yast issue, and sorry, there are two issues here (both minor): 1. It would probably reduce your support requirements and user frustration if you remind the user at the end of an upgrade that a reboot is necessary. 2. Somehow this kernel 2.6.18.2-33 installation was very odd. It added a new entry to the boot menu that displayed the kernel version and was the default. This was OK, but after the next kernel update, the system would not autoboot because kernel 2.6.18.2-33 had been removed but was still listed as the default in the boot menu. It was easy to boot another kernel, but I had to manually edit the menu to get rid of the unwanted menu item and attach the default to the most recently installed kernel. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 lslezak@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lslezak@novell.com |locilka@novell.com ------- Comment #8 from lslezak@novell.com 2007-02-27 08:50 MST ------- The message should printed by inst_suseconfig.ycp, it uses Kernel::GetInformAboutKernelChange(). (Ad 2. in comment #6 - that's probably a bug in the kernel postinstall script.) -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lslezak@novell.com Status|NEW |NEEDINFO Info Provider| |kern@sibbald.com Summary|Your handling of upgrading |Handling of upgrading kernel during System |to kernel 2.6.18.2-33 causes|Update causes confusion |confusion | ------- Comment #9 from locilka@novell.com 2007-02-28 02:24 MST ------- During the inst_suseconfig run (at the end of the system update), this message is reported in case of a kernel-update: ----------message---------- Reboot your system to activate the new kernel. ----------message---------- if (Kernel::GetInformAboutKernelChange ()) returns true. This is set by inst_kickoff using Kernel::SetInformAboutKernelChange () Anyway, Kernel YCP module is responsible for selecting the kernel and inst_kickoff just uses this information. Kern, it seems, we need your YaST logs. Attach the entire /var/log/YaST/ directory in a tar.gzip/bzip2 archive, please. http://en.opensuse.org/Bugs/YaST Thanks -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 ------- Comment #10 from kern@sibbald.com 2007-02-28 03:10 MST ------- Created an attachment (id=121496) --> (https://bugzilla.novell.com/attachment.cgi?id=121496&action=view) Tar of /var/log/YaST2 -- unpacks into YaST2 Hopefully this will provide what you need. One minor problem -- I am not sure what machine this occurred on (I will remember for the next bug report). I *believe* this happened on my development machine, from where I made the tar, but it could be my old test machine. If this tar file does not have the correct info, please close the bug report since the test machine had a total disk data loss (due to a kernel SCSI bug). -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 locilka@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsuchome@novell.com Severity|Minor |Enhancement Status|NEEDINFO |RESOLVED Info Provider|kern@sibbald.com | Resolution| |LATER ------- Comment #11 from locilka@novell.com 2007-03-07 07:42 MST ------- OK, enhancement. YaST system update could inform about need to reboot at the end instead of at the beginning. However, wasn't this an update using patches? Or did you really call 'yast2 update' didn't you rather call '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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 ------- Comment #12 from kern@sibbald.com 2007-03-08 02:23 MST ------- OK for the enhancement -- thanks. Update with patches? Well, that is a good (difficult) question -- I didn't realize that it was important. Typically, I click on the little orange tray icon ball when it has an exclamation, which I assume does "online_update", so I imagine that is what I did. However, from time to time, I open the Yast administrator (yast2) and apply part or all of the updates. Sorry, I cannot confirm which I did. In the future, I will pay more attention to remember the context. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=226036 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=226036#c13 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|LATER | --- Comment #13 from Stephan Kulow <coolo@novell.com> 2008-06-25 03:19:30 MDT --- mass reopening all 10.2 LATER+REMIND bugs. -- 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=226036 User coolo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=226036#c14 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |WONTFIX --- Comment #14 from Stephan Kulow <coolo@novell.com> 2008-06-25 03:23:46 MDT --- close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on 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.
participants (1)
-
bugzilla_noreply＠novell.com