Bug 1651209 - software update page shows incorrect kernel
Summary: software update page shows incorrect kernel
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: cockpit
Version: 29
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Martin Pitt
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-11-19 12:30 UTC by Andy Burns
Modified: 2018-11-19 17:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 17:52:42 UTC


Attachments (Terms of Use)
screenshot (201.31 KB, image/png)
2018-11-19 16:07 UTC, Andy Burns
no flags Details

Description Andy Burns 2018-11-19 12:30:32 UTC
Description of problem:
Software updates page within cockpit shows incorrect kernel version, when multiple kernels are installed 

Version-Release number of selected component (if applicable):
182-1.fc29

How reproducible:
100%

Steps to Reproduce:
visit the URL
<https://localhost:9090/updates>
hover over any of the kernel items listed for tooltip

Actual results:
tooltip shows e.g. "kernel 4.18.13-200.fc28"

Expected results:
tooltip should show the running kernel version i.e. "kernel 4.19.2-300.fc29"

Additional info:
# uname -a
Linux tower 4.19.2-300.fc29.x86_64 #1 SMP Wed Nov 14 19:05:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

# dnf list installed kernel.x86_64
Installed Packages
kernel.x86_64          4.18.17-200.fc28       @updates
kernel.x86_64          4.18.17-300.fc29       @updates
kernel.x86_64          4.19.2-300.fc29        @updates

Comment 1 Andy Burns 2018-11-19 12:33:50 UTC
I have realised that the version shown "4.18.13-200.fc28" isn't even one of the kernels versions that are installed!

Comment 2 Andy Burns 2018-11-19 12:45:23 UTC
This machine was upgraded from fc28 to fc29 using dnf-plugin-system-upgrade

dnf does seem to have some cached files related to kernel 4.18.13

# find / -name "*4.18.13*"
/var/lib/dnf/yumdb/k/6bec999f4bbdb2ac196600096e1e6639af36fb71-kernel-modules-extra-4.18.13-200.fc28-x86_64
/var/lib/dnf/yumdb/k/cd584632a155bec17d856c43644bd20995443fd2-kernel-devel-4.18.13-200.fc28-x86_64
/var/lib/dnf/yumdb/k/efc2de1f1f2e5c553de587c66b1d97dd866c7875-kernel-modules-4.18.13-200.fc28-x86_64
/var/lib/dnf/yumdb/k/046dc31d2f35e73357939bc4017098002eb8a9e3-kernel-4.18.13-200.fc28-x86_64
/var/lib/dnf/yumdb/k/1716b8af0160325176f2a5893a42a2b6f62afb70-kernel-core-4.18.13-200.fc28-x86_64

Running "dnf clean all" didn't alter the incorrect version numbers being reported.

Comment 3 Martin Pitt 2018-11-19 15:47:46 UTC
The only tooltip that show a version number are the ones in the "Update History" list. Do you mean these? As in the "available updates" list the version number is in a table column, not a tooltip.

So that means nothing else than that somewhere in the past that particular kernel got updated.

Perhaps send a screenshot? Right now I don't see anything wrong here.

Note that the software updates page is like "dnf updateinfo info", it has no idea what a kernel is or which one is running. It just knows about package versions.

Comment 4 Andy Burns 2018-11-19 16:07:18 UTC
Created attachment 1507304 [details]
screenshot

I'm curious where cockpit (or packagekit?) has plucked this version 4.18.13-200.fc28 from, as it is not a kernel version that is currently installed on the machine?

Though from the files in /var/lib/dnf/yumdb it is probably a version I had installed in the past.

Comment 5 Martin Pitt 2018-11-19 16:20:45 UTC
Right, that's the update history. This should correspond to the last record in "pkcon get-transactions". Something like

Transaction: /13875_eceaecdb
 System time: 2018-11-19T12:18:11.947988Z
 Succeeded: True
 Role: update-packages
 Duration: 341585 (seconds)
 Command line: 
 User ID: 1000
 Username: martin
 Real name: Martin Pitt
 Affected packages:
 - downloading zchunk-libs-0.9.15-1.fc29.x86_64
 - downloading vim-minimal-2:8.1.527-1.fc29.x86_64
[...]

Comment 6 Andy Burns 2018-11-19 17:52:42 UTC
OK, I guess it's just "unfortunate" that it sees the old kernel cleanup, as it occurs after the new kernel download/install

# pkcon get-transactions | grep kernel-4
 - downloading kernel-4.18.18-300.fc29.x86_64
 - downloading kernel-4.19.2-300.fc29.x86_64
 - downloading kernel-4.19.2-300.fc29.x86_64
 - installing kernel-4.19.2-300.fc29.x86_64
 - cleanup kernel-4.18.13-200.fc28.x86_64


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