Red Hat Bugzilla – Bug 599741
fv_ tests fail when libvirt is installed, but libvirtd is not started
Last modified: 2010-09-21 08:56:22 EDT
Description of problem:
fv_ tests fail when libvirt is installed, but libvirtd is not started:
error: unable to connect to '/var/run/libvirt/libvirt-sock', libvirtd may need to be started: Connection refused
error: failed to connect to the hypervisor
This happens when libvirt is installed via "v7 plan" and resulting prompts that use yum to install libvirt.
A work-around is to reboot or start libvird manually.
Version-Release number of selected component (if applicable):
v7 1.1 R3
Created attachment 423111 [details]
fvtest.py patch adding libvirtd startup code
This bug is reproduced in v7-1.2-3 and verified in v7-1.2-23.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
The libvirtd service is now properly started when required.