[Bug 555222] New: zypper dup should check if mkinitrd succeeds

http://bugzilla.novell.com/show_bug.cgi?id=555222 Summary: zypper dup should check if mkinitrd succeeds Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Update Problems AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mail@philipp-wagner.com QAContact: jsrain@novell.com Found By: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; de; rv:1.9.1.0) Gecko/20090623 SUSE/3.5.0-7.1 Firefox/3.5 I updated from 11.1 to 11.2 using zypper dup. My /boot partition was full and mkinitd during the installation of the kernel image probably failed. I didn't see the message as I let the update run unattended and only saw the last lines of output from zypper dup, which seemed to suggest that everything went ok. When rebooting I got a "kernel panic: attempted to kill init". Fortunately I had another kernel installed and were able to boot, remove some old files from /boot and call mkinitrd again. Now the system boots fine. A full /boot partition is not that unlikely (the default partition layout suggests a rather small /boot and installing two testkernels is enough to fill it so that mkinitrd fails. Could zypper dup give a summary of errors that happened while installing all packages in the end of the upgrade process so that the user sees this error before rebooting? Reproducible: Always -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555222#c shuang qiu <sqiu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |jkupec@novell.com |ovo.novell.com | Severity|Normal |Minor -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555222#c1 Ján Kupec <jkupec@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Status|NEW |NEEDINFO Info Provider| |kernel-maintainers@forge.pr | |ovo.novell.com AssignedTo|jkupec@novell.com |zypp-maintainers@forge.prov | |o.novell.com --- Comment #1 from Ján Kupec <jkupec@novell.com> 2009-11-18 10:56:36 UTC --- (In reply to comment #0)
I updated from 11.1 to 11.2 using zypper dup. My /boot partition was full and mkinitd during the installation of the kernel image probably failed. I didn't see the message as I let the update run unattended and only saw the last lines of output from zypper dup, which seemed to suggest that everything went ok.
You can see the message in /var/log/zypp/history
When rebooting I got a "kernel panic: attempted to kill init". Fortunately I had another kernel installed and were able to boot, remove some old files from /boot and call mkinitrd again. Now the system boots fine.
A full /boot partition is not that unlikely (the default partition layout suggests a rather small /boot and installing two testkernels is enough to fill it so that mkinitrd fails.
Could zypper dup give a summary of errors that happened while installing all packages in the end of the upgrade process so that the user sees this error before rebooting?
This is a bit difficult, as it needs introducing some infrastructure and coordination accross the distro (or even distros): packages need to report such errors somewhere where zypper could read them. We are actually discussing this on zypp-devel mailing list, but (i guess due to the combination of the level of difficulty, severity and lack of time) no one started implementation yet. Maybe simply reporting packages which wrote some messages to stderr could be a good start? But as far as this bug is concerned, shouldn't installation of the kernel package fail in such case? -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555222#c2 --- Comment #2 from Philipp Wagner <mail@philipp-wagner.com> 2009-11-18 11:06:34 UTC --- Created an attachment (id=328138) --> (http://bugzilla.novell.com/attachment.cgi?id=328138) zypper dup log I've attached a part of the /var/log/zypp/history file which shows the mkinitrd failure. The installation continues as usual afterwards. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555222#c3 Michal Marek <mmarek@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|kernel-maintainers@forge.pr | |ovo.novell.com | --- Comment #3 from Michal Marek <mmarek@novell.com> 2009-11-18 13:23:41 UTC --- The log shows installation of the suspend package, not the kernel, so it either a bug in mkinitrd that doesn't return failure or in suspend %post that ignores it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=555222 http://bugzilla.novell.com/show_bug.cgi?id=555222#c4 --- Comment #4 from Philipp Wagner <mail@philipp-wagner.com> 2009-11-19 09:28:19 UTC --- Created an attachment (id=328394) --> (http://bugzilla.novell.com/attachment.cgi?id=328394) log of kernel installation I attached a bit bigger part of the history log. I don't know why there were only two kernels while installing the kernel package but three on the suspend package. I guess a package made a backup of the kernel between the two steps. -- Configure bugmail: http://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=555222 https://bugzilla.novell.com/show_bug.cgi?id=555222#c5 Michael Andres <ma@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #5 from Michael Andres <ma@suse.com> 2014-01-13 11:02:45 CET --- Meanwhile fixed bug in %post 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.
participants (1)
-
bugzilla_noreply@novell.com