Bug 1200994 - vdsmd service fails to start on boot because libvirt socket is not ready yet
Summary: vdsmd service fails to start on boot because libvirt socket is not ready yet
Keywords:
Status: CLOSED DUPLICATE of bug 1200991
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.6
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Yaniv Bronhaim
QA Contact: Gil Klein
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-03-11 18:53 UTC by Dima Kuznetsov
Modified: 2015-03-12 13:11 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-03-12 13:11:37 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
/var/log/boot.log from a system that exhibited this issue. (9.98 KB, application/octet-stream)
2015-03-11 18:53 UTC, Dima Kuznetsov
no flags Details

Description Dima Kuznetsov 2015-03-11 18:53:12 UTC
Created attachment 1000618 [details]
/var/log/boot.log from a system that exhibited this issue.

Description of problem:
When booting on EL6 platform, vdsmd service fails to start while running 'vdsm-tool nwfilter' because libvirt socket file is not present yet

See attached boot.log

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

How reproducible:
Sometimes

Steps to Reproduce:
1. Boot
2. Check if vdsmd is up
3.

Actual results:
vdsmd is not running, starting manually workd

Expected results:
vdsmd running from the start

Additional info:
As with most races, I have not way to reliable reproduce it. 

Document URL: 

Section Number and Name: 

Describe the issue: 

Suggestions for improvement: 

Additional information: 


Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Dan Kenigsberg 2015-03-11 23:33:01 UTC
/var/log/libvirt/libvirtd.log may give a hint why libvirtd was slow to start in this instance.


On el7/Fedora we have better chance to use systemd so that vdsm is started only after libvirtd is serving. But on el6 I don't see a real solution to this.

we wait 10 seconds

 utils.retry(libvirtOpen, timeout=10, sleep=0.2)
 
we can retry twice as much. But not much more.

Comment 2 Oved Ourfali 2015-03-12 13:11:37 UTC

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


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