[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
http://bugzilla.novell.com/show_bug.cgi?id=555222#c1
Ján Kupec
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
http://bugzilla.novell.com/show_bug.cgi?id=555222#c3
Michal Marek
http://bugzilla.novell.com/show_bug.cgi?id=555222
http://bugzilla.novell.com/show_bug.cgi?id=555222#c4
--- Comment #4 from Philipp Wagner
https://bugzilla.novell.com/show_bug.cgi?id=555222
https://bugzilla.novell.com/show_bug.cgi?id=555222#c5
Michael Andres
participants (1)
-
bugzilla_noreply@novell.com