Bug 1023966 - hosted-engine fails if libvirtd is down
Summary: hosted-engine fails if libvirtd is down
Keywords:
Status: CLOSED DUPLICATE of bug 1025350
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-setup
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 3.3.0
Assignee: Sandro Bonazzola
QA Contact: Leonid Natapov
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-28 13:07 UTC by Yedidyah Bar David
Modified: 2013-11-10 11:55 UTC (History)
4 users (show)

Fixed In Version: ovirt-hosted-engine-setup-1.0.0-0.8.beta3.el6ev
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-08 08:54:33 UTC
oVirt Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Yedidyah Bar David 2013-10-28 13:07:57 UTC 
Description of problem:

hosted-engine fails if libvirtd is down

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

How reproducible:

Steps to Reproduce:
1. service libvirtd stop
2. hosted-engine --deploy

Actual results:

[ ERROR ] Failed to execute stage 'Environment customization': Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

Expected results:

hosted-engine should start libvirtd if it's down and continue.
It should also configure it to start on reboot.

Additional info:
Comment 1 Sandro Bonazzola 2013-10-28 13:43:40 UTC 
(In reply to Yedidyah Bar David from comment #0)
> [ ERROR ] Failed to execute stage 'Environment customization': Failed to
> connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

Can you attach full logs?
On upstream starting vdsmd also start supervdsmd and libvirtd and AFAIK it worked like that at least a few weeks ago.
Comment 2 Sandro Bonazzola 2013-11-08 08:54:33 UTC 
I'm not able to reproduce this with 
ovirt-hosted-engine-setup-1.0.0-0.8.beta3.el6ev.
I think that libvirtd missing was due to vdsm changes, so I'm marking this as duplicate.

*** This bug has been marked as a duplicate of bug 1025350 ***
Note You need to log in before you can comment on or make changes to this bug.