Bug 1971423
| Summary: | Module kvdo not found in directory /lib/modules/4.18.0-310.el8.x86_64 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Martin Pitt <mpitt> |
| Component: | kmod-kvdo | Assignee: | Andy Walsh <awalsh> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | vdo-qe |
| Severity: | unspecified | Docs Contact: | |
| Priority: | high | ||
| Version: | CentOS Stream | CC: | awalsh, bstinson, carl, cwei, jwboyer |
| Target Milestone: | beta | Keywords: | Regression |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-06-24 17:58:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Martin Pitt
2021-06-14 05:20:44 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. 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? 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. My testing indicates that this problem is resolved. |