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 1140604 - Updating RHEL 7.0 -> 7.1, yum prints error "libvirtd.socket: command not found"
Summary: Updating RHEL 7.0 -> 7.1, yum prints error "libvirtd.socket: command not found"
Keywords:
Status: CLOSED DUPLICATE of bug 1136736
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-11 10:32 UTC by Richard W.M. Jones
Modified: 2014-09-11 10:39 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-11 10:39:12 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Richard W.M. Jones 2014-09-11 10:32:50 UTC
Description of problem:

When updating from libvirt-1.1.1-29.el7.x86_64 to
libvirt-1.2.8-2.el7.x86_64, libvirt %post script prints
this warning:

  Cleanup    : libvirt-daemon.x86_64                                      30/33 
/var/tmp/rpm-tmp.fCGAAr: line 8: libvirtd.socket: command not found
error: %preun(libvirt-daemon-1.2.8-1.el7.x86_64) scriptlet failed, exit status 127
Error in PREUN scriptlet in rpm package libvirt-daemon
  Cleanup    : libvirt-docs-1.1.1-29.el7.x86_64                           31/33 
error: libvirt-daemon-1.2.8-1.el7.x86_64: erase failed
  Cleanup    : libvirt-client-1.1.1-29.el7.x86_64                         32/33 

and then later this error:

libvirt-daemon-1.2.8-1.el7.x86_64 was supposed to be removed but is not!

and then:

$ rpm -q libvirt-daemon
libvirt-daemon-1.2.8-1.el7.x86_64
libvirt-daemon-1.2.8-2.el7.x86_64

I'm fairly sure I didn't have the libvirt-daemon-1.2.8-1.el7.x86_64
package installed before I started.  Not sure how it could have been
installed on its own?

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

old: libvirt-1.1.1-29.el7.x86_64
new: libvirt-1.2.8-2.el7.x86_64

How reproducible:

Once.

Comment 1 Richard W.M. Jones 2014-09-11 10:34:42 UTC
It looks like I did install libvirt-daemon-1.2.8-1.el7.x86_64
on its own before (alongside the old libvirt).  In any case I now
cannot remove it:

Running transaction
/var/tmp/rpm-tmp.NM9cdZ: line 8: libvirtd.socket: command not found
error: %preun(libvirt-daemon-1.2.8-1.el7.x86_64) scriptlet failed, exit status 127
Error in PREUN scriptlet in rpm package libvirt-daemon-1.2.8-1.el7.x86_64
  Verifying  : libvirt-daemon-1.2.8-1.el7.x86_64                            1/1 

Failed:
  libvirt-daemon.x86_64 0:1.2.8-1.el7                                           

So maybe the error here is that libvirt-daemon cannot be removed?

Comment 3 Daniel Berrangé 2014-09-11 10:39:12 UTC
Yes, this is a bug in the libvirt-daemon-1.2.8-1.el7.x86_64 package. You'll need to use  'rpm -e --noscripts libvirt-daemon-1.2.8-1.el7.x86_64' to kill it.

https://bugzilla.redhat.com/show_bug.cgi?id=1136736

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


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