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 1578218 - upgrade error
Summary: upgrade error
Keywords:
Status: CLOSED DUPLICATE of bug 1574572
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: kmod-kvdo
Version: 7.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Joseph Chapman
QA Contact: vdo-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-05-15 04:18 UTC by Dmitry Melekhov
Modified: 2021-09-03 12:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-26 20:20:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dmitry Melekhov 2018-05-15 04:18:18 UTC
Description of problem:


Version-Release number of selected component (if applicable):


How reproducible:

always


Steps to Reproduce:

yum update

Actual results:


modprobe: FATAL: Module kvdo is in use.
modprobe: FATAL: Module uds is in use.
error: %preun(kmod-kvdo-6.1.0.153-15.el7.x86_64) scriptlet failed, exit status 1
Error in PREUN scriptlet in rpm package kmod-kvdo-6.1.0.153-15.el7.x86_64
  Очистка     : ca-certificates-2017.2.20-71.el7.noarch                                                                    79/94 
error: kmod-kvdo-6.1.0.153-15.el7.x86_64: erase failed


Expected results:


Installation without errors.

Comment 2 Dennis Keefe 2018-05-16 03:05:07 UTC
This looks like a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1574572

Comment 3 Jakub Krysl 2018-05-16 07:28:42 UTC
(In reply to Dennis Keefe from comment #2)
> This looks like a duplicate of
> https://bugzilla.redhat.com/show_bug.cgi?id=1574572

This BZ speaks of 'erase failed', but lacks the information of the final status. BZ1574572 has the same part:
> modprobe: FATAL: Module kvdo is in use.
> modprobe: FATAL: Module uds is in use.
> error: %preun(kmod-kvdo-6.1.0.153-15.el7.x86_64) scriptlet failed, exit status 1
> Error in PREUN scriptlet in rpm package kmod-kvdo-6.1.0.153-15.el7.x86_64
> error: kmod-kvdo-6.1.0.153-15.el7.x86_64: erase failed

Although it seems each BZ is asking for different thing. BZ1574572 asks for no update but this BZ asks for the update to finish without errors, which afaik cannot be done as long as the modules are loaded and cannot be removed.

Comment 4 Matthew Sakai 2018-06-28 19:54:40 UTC
Assigning this to Joe since he has https://bugzilla.redhat.com/show_bug.cgi?id=1574572 also, and may need to take this issue into account.

Comment 5 Andy Walsh 2018-09-26 20:20:14 UTC

*** This bug has been marked as a duplicate of bug 1574572 ***


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