Bug 1200994
| Summary: | vdsmd service fails to start on boot because libvirt socket is not ready yet | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Dima Kuznetsov <dkuznets> | ||||
| Component: | vdsm | Assignee: | Yaniv Bronhaim <ybronhei> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Gil Klein <gklein> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.6 | CC: | bazulay, ecohen, gklein, iheim, lsurette, mgoldboi, oourfali, rbalakri, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | infra | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2015-03-12 13:11:37 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
/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. *** This bug has been marked as a duplicate of bug 1200991 *** |
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: