Description of problem: If you have an older kernel running (more than two newer kernels available) yum erases the running kernel. This leads to big problems if you have to load a not already loaded kernel module or if you restart the firewall. Version-Release number of selected component (if applicable): yum-3.2.13-2.fc9
I wonder if we're getting caught up by the change in kernel binary naming. Although it looks like it's okay from a quick look
I guess I'm not just lucky then; f8>f9beta>updated: $ rpm -qa kernel\*|sort kernel-2.6.25-0.201.rc8.git4.fc9.i686 kernel-2.6.25-0.204.rc8.git4.fc9.i686 kernel-2.6.25-0.218.rc8.git7.fc9.i686 kernel-devel-2.6.25-0.218.rc8.git7.fc9.i686 kernel-headers-2.6.25-0.218.rc8.git7.fc9.i386 kerneloops-0.10-11.fc9.i386 $ uname -a Linux poweredge 2.6.25-0.195.rc8.git1.fc9.i686 #1 SMP Thu Apr 3 09:42:34 EDT 2008 i686 i686 i386 GNU/Linux
Created attachment 302192 [details] var/log/messages filtered to include kernel, yum and errors Notice that as well as nuking the running kernel: Apr 12 00:05:01, there is getting two messages into the log stating the same kernel has been installed. It seems the second one of these should actually be the Removed: kernel-x.y.z message {although I know version-release isn't normally logged for removals - it would be better if it did.}
Reproduced and pushed the fix upstream