Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
On a system where the "kmod-kvdo" package is installed, and the kvdo module has been added to the kernel via "modprobe" (e.g.: via a "vdo create" or "vdo start" command), running the "modinfo kvdo" program does not display the version of the currently running kvdo module.
This leads to confusion in situations where the kmod-kvdo package is being upgraded. One example is in BZ 1510176, "yum remove kmod-kvdo does not unload kernel module".
Version-Release number of selected component (if applicable):
kmod-kvdo-6.1.0.34-7
How reproducible:
100%
Steps to Reproduce:
1. Install the "kmod-kvdo" and "vdo" packages (or select a base installation option).
2. Run "sudo vdo create" to create a VDO volume on a spare storage device. (Alternatively, run "sudo modprobe kvdo"
3. Run "modinfo kvdo".
Actual results:
[root@rhel75test-20171023 ~]# modinfo kvdo
filename: /lib/modules/3.10.0-768.el7.x86_64/weak-updates/kmod-kvdo/vdo/kvdo.ko
version:
license: GPL
author: Red Hat, Inc.
description: device-mapper target for transparent deduplication
rhelversion: 7.5
depends: uds,dm-mod
vermagic: 3.10.0-766.el7.x86_64 SMP mod_unload modversions
Expected results:
The "version" field displays a version number that matches with the kmod-kvdo package that was installed at the time of executing "modprobe kvdo".
Additional info:
I assume this will fix the 'vdo status' version as well?
[root@mckinley-04 ~]# vdo status | more
VDO status:
Date: '2017-11-10 14:32:28-06:00'
Node: mckinley-04.lab.msp.redhat.com
Kernel module:
Loaded: true
Name: kvdo
Version information:
kvdo version: null
[...]
(In reply to Corey Marthaler from comment #2)
> I assume this will fix the 'vdo status' version as well?
>
> [root@mckinley-04 ~]# vdo status | more
> VDO status:
> Date: '2017-11-10 14:32:28-06:00'
> Node: mckinley-04.lab.msp.redhat.com
> Kernel module:
> Loaded: true
> Name: kvdo
> Version information:
> kvdo version: null
>
> [...]
Yes; the version string from "modinfo kvdo" should print right after "kvdo version".
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHEA-2018:0900