Bug 988391 - After update to F19 from F18, the latest kernel is now older than current kernel
After update to F19 from F18, the latest kernel is now older than current kernel
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
x86_64 Linux
unspecified Severity low
: ---
: ---
Assigned To: Kernel Maintainer List
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2013-07-25 09:39 EDT by Red Hat Production Operations
Modified: 2013-07-25 09:49 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-07-25 09:49:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Red Hat Production Operations 2013-07-25 09:39:07 EDT
Description of problem:

Updated from F18 -> F19 using:

  yum --releasever=19 --disableplugin=presto distro-sync -y

and now, yum list updates shows:

kernel-devel.x86_64                                                                                                  3.9.9-302.fc19                                                                                          updates
kernel-modules-extra.x86_64                                                                                          3.9.9-302.fc19                                                                                          updates

However, the current kernel installed is:


Why did we go backwards in version number for the kernel?
Comment 1 Josh Boyer 2013-07-25 09:49:49 EDT
F19 is in the middle of a rebase to the 3.10 kernel.  An update for 3.10.3 should be hitting the repositories shortly.

F18 won't rebase until a bit later, and there were fixes in the meantime so a newer build was pushed out.  This happens from time to time but we try to limit it as much as possible.

Note You need to log in before you can comment on or make changes to this bug.