Bugzilla – Bug 225674
system update reinstalls current kernel and removes prior kernel
Last modified: 2006-12-11 20:34:42 UTC
To reproduce: 1-install most recent kernel manually 2-reboot 3-run system update Actual results: 1-existing kernel and initrd are replaced with the same kernel 2-previous kernel left by manual installation of latest kernel is removed Expected results: 1-existing kernel and initrd remain untouched by the update 2-prior kernel remains installed I experienced this twice in two days. The first time was a recent update, probably to about rc2 with the 2.6.18.2-31-default kernel that I updated to 2.6.18.2-33 before starting the update. Following discussion of the behavior on the factory mailing list, I installed alpha4 purely to test this, and the 2.6.18_rc5_git6-2 was removed.
Created attachment 108036 [details] y2logRPM
Created attachment 108037 [details] y2log.SuSEconfig
Created attachment 108038 [details] y2log zipped
You have multiple kernel-defaults in the rpm DB: 2006-12-03 21:56:14 <2> m7ncd(4016) [rpm] RpmDb.cc(buildIndex):297 Multiple entries for package 'kernel-default' in rpmdb .... doUpgrade available: SKIP no candidate for I__s_[S0:0][package]kernel-default-2.6.18.2-33.i586 ResolverUpgrade.cc(doUpgrade):367 installed I__s_[S0:0][package]kernel-default-2.6.18_rc5_git6-2.i586, candidate U__s_@[S2:1][package]kernel-default-2.6.18.2-33.i586 So kernel-default-2.6.18.2-33.i586 will be installed for update again. This case is so special that we cannot handle it. If you want to keep your kernel you will have to lock it. Yes there is a bug concerning locking and permanent holding this state in the system too.
Your explanation is only slightly clearer than mud. If the upgrade process finds a match between any installed kernel and the kernel it intends to install, it should either find nothing to do regarding kernels, or ask for user input about what it proposes to do. This is certainly not currently resolved properly as WORKSFORME.