Bug 1115450 - When failing to connect to libvirt the process is stuck and there is no log
Summary: When failing to connect to libvirt the process is stuck and there is no log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-appliance
Version: 3.5
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.6.0
Assignee: Anatoly Litovsky
QA Contact: bugs@ovirt.org
URL:
Whiteboard: node
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-02 11:50 UTC by Liron Aravot
Modified: 2016-02-10 19:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-17 15:02:38 UTC
oVirt Team: Node
Embargoed:


Attachments (Terms of Use)

Description Liron Aravot 2014-07-02 11:50:43 UTC
Description of problem:
On failure to connect to libvirt:
1. there's no log, therefore it's not possible to know what's the issue and th
2. the process is stuck

How reproducible:
Always

Steps to Reproduce:
1. intentionally prevent succesfull connection to libvirt
2. attempt to make the image by 'make ovirt-appliance-fedora.raw'

Actual results:
the process is stuck, there's no log indicating what's the issue.

Expected results:
the execution shouldn't be stuck, there should be a log indicating what's the cuyrrent state.

Comment 1 Sandro Bonazzola 2014-10-17 12:14:35 UTC
Moving pending bugs not fixed in 3.5.0 to 3.5.1.

Comment 3 Sandro Bonazzola 2015-01-21 16:08:36 UTC
oVirt 3.5.1 has been released, re-targeting to 3.6.0 as not marked as urgent / high severity or priority

Comment 4 Liron Aravot 2015-04-06 08:09:13 UTC
Anatoly,
i performed the steps described in 
https://gerrit.ovirt.org/gitweb?p=ovirt-appliance.git;a=blob;f=engine-appliance/docs/introduction.md;hb=HEAD

iirc.


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