From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.0-0.99.11 i686; en-US; 0.7)
Upgrading my system from RHL7.0, I chose lilo to run and accepted the
default configuration of lilo with a linux and dos. Almost ran the
install, realized I'd like to go back and choose what packages were
upgraded, and backed up till I could choose whether to customize packages.
Didn't end up changing the upgraded packages, and continued through the
Lilo ended up getting ran, but it used my old lilo.conf (although it
deposited a lilo.conf.rpmsave which was bytewise identical).
Reproducible: Didn't try. Hard to revert an upgrade. 8^)
Actual Results: Result: It booted my default 2.2.18 kernel, and aborted
(kernel not new enough). Fortunately, I had a 2.4.1 test kernel in that
conf, so I could boot with that.
Expected Results: It should have added a default entry for the new kernel,
I've seen this happen once too.
Seems related to bug 26790.
Also bug 27952.
And bug 28752.
*** Bug 27952 has been marked as a duplicate of this bug. ***
*** Bug 28752 has been marked as a duplicate of this bug. ***
So far unable to reproduce.
Our installer team-lead thinks we should really fix this before next release.
Still no reproducable test case.
msw fixed this (it's a dup of another bug regarding upgrades from 3.0.3)
*** This bug has been marked as a duplicate of 31194 ***