Bug 1204533 - Offline update does not update kernel
Summary: Offline update does not update kernel
Keywords:
Status: CLOSED DUPLICATE of bug 1205649
Alias: None
Product: Fedora
Classification: Fedora
Component: PackageKit
Version: 21
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-22 23:27 UTC by John Haiducek
Modified: 2015-04-07 12:41 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-04-07 12:41:48 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
output from pkcon get-updates (17.52 KB, text/plain)
2015-04-07 11:13 UTC, John Haiducek
no flags Details
output from yum check-update (24.80 KB, text/plain)
2015-04-07 11:14 UTC, John Haiducek
no flags Details
Output from rpm -qa | sort (225.97 KB, text/plain)
2015-04-07 12:27 UTC, John Haiducek
no flags Details

Description John Haiducek 2015-03-22 23:27:04 UTC
Description of problem: The offline update tool updated my kernel-devel, kernel-tools etc. to 3.19.1-201, but did not update the kernel itself. When I run yum update it sees the new kernel available.


Version-Release number of selected component (if applicable):

kernel-3.18.7-200
kernel-devel-3.19.1-201
PackageKit-1.0.4-1


How reproducible:

Problem persisted through two offline updates.


Steps to Reproduce:
1. Use the software update GUI to install updates
2. Reboot
3. Check kernel/kernel-devel versions

Actual results:

kernel package should be upgraded

Expected results:

kernel-devel is upgraded but kernel isn't.

Additional info:

Comment 1 Kamil Páral 2015-04-03 13:20:42 UTC
Do you perhaps have virtualbox or nvidia drivers installed? In that case this would be bug 1205649.

Comment 2 John Haiducek 2015-04-03 15:15:21 UTC
No, I don't have nvidia or virtualbox drivers.

Comment 3 Kamil Páral 2015-04-07 08:26:11 UTC
When you have your system in a state where packagekit hasn't updated your kernel (ideally after offline upgrade has been run, and you find out it skipped your kernel), can you attach output from `pkcon get-updates` and `yum check-update`?

Comment 4 John Haiducek 2015-04-07 11:13:46 UTC
Created attachment 1011694 [details]
output from pkcon get-updates

Comment 5 John Haiducek 2015-04-07 11:14:17 UTC
Created attachment 1011695 [details]
output from yum check-update

Comment 6 John Haiducek 2015-04-07 11:18:13 UTC
(In reply to Kamil Páral from comment #3)
> When you have your system in a state where packagekit hasn't updated your
> kernel (ideally after offline upgrade has been run, and you find out it
> skipped your kernel), can you attach output from `pkcon get-updates` and
> `yum check-update`?

Just attached both of those. My system is currently in the state of having an out-of-date kernel (but up-to-date kernel headers). It's been a few weeks since this first happened; I don't remember for sure if I've installed any updates in the meantime but I made a point to at least leave the kernel and related packages alone.

Comment 7 Kamil Páral 2015-04-07 12:08:26 UTC
Hmm, you have akmod-wl installed, which is close to one of the packages we identified to be potentially causing packagekit issues in bug 1205649 comment 13. But you have the akmod version, not kmod, which is something a bit different.

Can you please run
$ rpm -qa | sort > packages
and attach the "packages" file? Thanks.

Comment 8 John Haiducek 2015-04-07 12:27:21 UTC
Created attachment 1011742 [details]
Output from rpm -qa | sort

Comment 9 John Haiducek 2015-04-07 12:27:58 UTC
(In reply to Kamil Páral from comment #7)
> Can you please run
> $ rpm -qa | sort > packages
> and attach the "packages" file? Thanks.

Done.

Comment 10 Kamil Páral 2015-04-07 12:41:48 UTC
You have kmod-wl-<kernel_version> packages installed. That explains everything, this is the same issue as bug 1205649. Closing as a duplicate. Please follow that bug for updates.

*** This bug has been marked as a duplicate of bug 1205649 ***


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