Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:

libvirt qemu:///session URLs are broken.  See the end of the build
log here:

http://download.devel.redhat.com/brewroot/work/tasks/2686/7922686/build.log

libvirt: XML-RPC error : Failed to connect socket to '/builddir/.cache/libvirt/libvirt-sock': No such file or directory
libguestfs: error: could not connect to libvirt (URI = qemu:///session): Failed to connect socket to '/builddir/.cache/libvirt/libvirt-sock': No such file or directory [code=38 domain=7]

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

libvirt-devel-1.2.8-1.el7.x86_64

How reproducible:

100%

Steps to Reproduce:
1. Build libguestfs and run 'make quickcheck'

I'm able to reproduce this using:

rm -rf /tmp/p
mkdir -p /tmp/p/.cache
killall libvirtd
export LIBVIRT_DEBUG=1
export HOME=/tmp/p
export XDG_RUNTIME_DIR=/tmp/p/.cache
libguestfs-test-tool

Note that /tmp/p/.cache/libvirt does not exist in this scenario.
I would have expected libvirt to create the directory if it does
not exist, but apparently it does not.

(You get the same error if /tmp/p/.cache doesn't exist too)

Downgrading to libvirt 1.1.1-29.el7 fixes the problem, therefore this
seems to be a regression between releases.

Hmm, looks like another regression caused by the socket activation code. The socket is no longer created by libvirtd but it's created by the client and passed to the daemon as a file descriptor.

FYI same thing is now happening in Rawhide, eg:

https://kojipkgs.fedoraproject.org//work/tasks/2029/7532029/build.log

Fix proposed upstream:

https://www.redhat.com/archives/libvir-list/2014-September/msg00374.html

*** Bug 1140624 has been marked as a duplicate of this bug. ***

I can confirm this is a dup of Bug 927369, the issue is beaing dealt with in there (since it cause it as well).

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