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.
Bug 1971423 - Module kvdo not found in directory /lib/modules/4.18.0-310.el8.x86_64
Summary: Module kvdo not found in directory /lib/modules/4.18.0-310.el8.x86_64
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: kmod-kvdo
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: beta
: ---
Assignee: Andy Walsh
QA Contact: vdo-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-14 05:20 UTC by Martin Pitt
Modified: 2021-09-06 15:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-06-24 17:58:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Martin Pitt 2021-06-14 05:20:44 UTC 
Description of problem: Same issue again as in bug 1894978 (and lots of earlier ones). Current CentOS 8 stream has a new kernel without a corresponding kvdo.


Version-Release number of selected component (if applicable): 6.2.4.26-77.el8


How reproducible: Always


Steps to Reproduce:
1. modprobe kvdo
Comment 1 Andy Walsh 2021-06-14 13:17:19 UTC 
This has been requested to be updated for nearly two weeks in the CPE queue.  When I followed up on the request last week, I was told it would be updated that day.  My guess is that it will be updated soon.  I will follow up again.
Comment 2 Carl George 🤠 2021-06-16 19:05:02 UTC 
I'm not a kmod expert, but I'm not accustomed to seeing the directory match exactly.  For example, in public RHEL 8.4, we have:

- kernel-4.18.0-305.3.1.el8_4
- kmod-kvdo-6.2.4.26-77.el8 with files in /lib/modules/4.18.0-294.el8.x86_64/

In the RHEL 8.5 nightly compose, we have:

- kernel-4.18.0-312.el8
- kmod-kvdo-6.2.5.11-78.el8 with files in /lib/modules/4.18.0-305.5.el8.x86_64/

I can see the latest export to git.centos.org is kmod-kvdo-6.2.5.41-78.el8.  Was that build attached to errata and later dropped?  Should I build and ship that in CS8 or opt for the previous kmod-kvdo-6.2.5.11-78.el8 export to match RHEL 8.5?  Also I was wondering why does kmod-kvdo go directly from 6.2.5.11-78 to 6.2.5.41-78 without resetting the release to 1?
Comment 3 Andy Walsh 2021-06-17 00:46:49 UTC 
kmod-kvdo-6.2.5.41-78.el8 should be built and shipped in CS8.(In reply to Carl George 🤠 from comment #2)
> I'm not a kmod expert, but I'm not accustomed to seeing the directory match
> exactly.  For example, in public RHEL 8.4, we have:
> 
> - kernel-4.18.0-305.3.1.el8_4
> - kmod-kvdo-6.2.4.26-77.el8 with files in /lib/modules/4.18.0-294.el8.x86_64/
> 
> In the RHEL 8.5 nightly compose, we have:
> 
> - kernel-4.18.0-312.el8
> - kmod-kvdo-6.2.5.11-78.el8 with files in
> /lib/modules/4.18.0-305.5.el8.x86_64/
> 
> I can see the latest export to git.centos.org is kmod-kvdo-6.2.5.41-78.el8. 
> Was that build attached to errata and later dropped?  

No.  And since you asked I decided to take a look.  Apparently I did not add this build to the errata.  It has been now.


> Should I build and ship that in CS8 or opt for the previous 
> kmod-kvdo-6.2.5.11-78.el8 export to match RHEL 8.5?

Yes, please build and ship kmod-kvdo-6.2.5.41-78.el8 to match RHEL-8.5.


> Also I was wondering why does kmod-kvdo go directly from
> 6.2.5.11-78 to 6.2.5.41-78 without resetting the release to 1?

I've typically followed the process of only resetting Release to 1 on a major version (7 to 8) or a rebase.  With the way versioning for the VDO code works, the Release field would only ever change for a rebuild due to kABI changes and I think that doesn't line up quite so well with actual spec changes that are needed to go in.  Happy to talk offline about this if you'd like.
Comment 4 Andy Walsh 2021-06-24 17:58:15 UTC 
My testing indicates that this problem is resolved.
Note You need to log in before you can comment on or make changes to this bug.