https://bugzilla.novell.com/show_bug.cgi?id=873537
https://bugzilla.novell.com/show_bug.cgi?id=873537#c2
Jon Nelson
Jon, to be sure: - there are partially installed kernels - grub2.cfg refers to kernels which don't exist?
I wonder especially about the 2nd part; no matter what the installed packager are (files in /boot are what matters), does grub2.cfg refer to a kernel which does not exist at all? And if it does and such kernel was uninstalled earlier, how was it uninstalled? Was it openSUSE kernel, some other?
Regarding the grub.cfg file (not grub2.cfg) referring to kernels which don't exist: The grub.cfg file is an accurate-ish representation of the contents of /boot. The "-ish" part comes in where only the 3.11.10 kernel *and* initrd are both present. Removing the 3.13.5 and 3.14.0-23 kernel *packagse* did not remove the /boot/vmlinuz-${version}... files. Removing the 3.11.6 kernel package didn't remove the 3.11.6 *initrd*. Removing the kernel packages didn't reset the /boot/initrd symlink to any version that exists. So, a bunch of issues, there. My *guess* is that grub2 is probably OK - it's finding kernels (regardless of whether they are complete or are installed by the rpm -- a reasonable and correct choice IMO) but the problem is that removing kernel packages doesn't appear to do the right thing. Yes, grub2.cfg is referring to a kernel that doesn't exist at all: file /boot/vmlinuz-3.14.0-23.gfa168d7-desktop is not owned by any 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.