Bug 1574572
Summary: | Upgrading kmod-kvdo rpm can lead to having different versions installed | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Jakub Krysl <jkrysl> |
Component: | kmod-kvdo | Assignee: | Joseph Chapman <jochapma> |
Status: | CLOSED DUPLICATE | QA Contact: | Jakub Krysl <jkrysl> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.5 | CC: | awalsh, bgurney, dennis.charipar, dm, jkrysl, limershe |
Target Milestone: | rc | ||
Target Release: | --- | ||
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: | 2018-09-26 20:23:36 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
Jakub Krysl
2018-05-03 14:55:58 UTC
This is due to a bug in yum and I've been unable to find a workaround. (In reply to Joseph Chapman from comment #2) > This is due to a bug in yum and I've been unable to find a workaround. I think the fix to this is described in BZ 1553420, please have look. *** Bug 1578218 has been marked as a duplicate of this bug. *** This is resolved via the resolution for BZ1553420. Despite having a different condition, I am closing this as a duplicate of that bug so that these can be linked. *** This bug has been marked as a duplicate of bug 1553420 *** Answerfile has been generated at /var/log/leapp/answerfile [root@localhost ~]# sudo dnf check kmod-kvdo-6.1.3.23-5.el7.x86_64 has installed conflict "kmod-kvdo": kmod-kvdo-6.1.3.23-5.el7.x86_64 I am trying to upgrade centos 7 to rocky Linex 8 but get this error message above. What is the workaround? Thanks hi @dennis.charipar, We don't have any way to fix this, as noted in Comment#2. Though the issue in Comment#3 shows that we added some output to indicate when there are reasons to prevent the removal of one version of kmod-kvdo for the next. Make sure that if you have a VDO volume on the system that you've unmounted and stopped any of the volumes before proceeding. If that doesn't work, then I don't believe we have a known fix for what you're seeing. All that being said, a workaround to this particular issue can be to just uninstall kmod-kvdo prior to performing the upgrade and then re-install it when you're finished. Did not intend to tag you for needinfo. Apologies. |