Bug 1420507
| Summary: | VDSM service keeps stopping on Fedora 25 | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] vdsm | Reporter: | jniederm | ||||||
| Component: | Core | Assignee: | Dan Kenigsberg <danken> | ||||||
| Status: | CLOSED WORKSFORME | QA Contact: | meital avital <mavital> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.20.0 | CC: | bugs, jniederm, michal.skrivanek | ||||||
| Target Milestone: | ovirt-4.2.0 | Flags: | rule-engine:
ovirt-4.2+
|
||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2017-08-22 07:48:22 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
when you see problem connecting to libvirt, obviously you need to gather/provide libvirt debugging information;) Created attachment 1249903 [details]
logs2.zip
vdsm.log and output of `journalctl --boot=-1 -u libvirtd -u vdsmd` with libvirtd log level set to DEBUG
dies on libvirt access. I suppose wrong libvirt(virt-preview) repos |
Created attachment 1248661 [details] logs.zip Description of problem: After several time vdsm service stops, repeatedly. I don't know whether it's spontaneous or triggered by some action in engine. Last lines of vdsm.log are: File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3701, in getLibVersion if ret == -1: raise libvirtError ('virConnectGetLibVersion() failed', conn=self) libvirtError: internal error: client socket is closed `systemctl start vdsmd` doesn't help. It's necessary to reboot host. 'libvirtd' service is running. Version-Release number of selected component (if applicable): libvirt-client.x86_64 3.0.0-1.fc25 libvirt-daemon.x86_64 3.0.0-1.fc25 libvirt-daemon-config-nwfilter.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-interface.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-network.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-nodedev.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-nwfilter.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-qemu.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-secret.x86_64 3.0.0-1.fc25 libvirt-daemon-driver-storage.x86_64 3.0.0-1.fc25 libvirt-daemon-kvm.x86_64 3.0.0-1.fc25 libvirt-libs.x86_64 3.0.0-1.fc25 libvirt-lock-sanlock.x86_64 3.0.0-1.fc25 libvirt-python.x86_64 3.0.0-1.fc25 vdsm.x86_64 4.20.0-341.git616caa9.fc25 vdsm-api.noarch 4.20.0-341.git616caa9.fc25 vdsm-hook-vmfex-dev.noarch 4.20.0-341.git616caa9.fc25 vdsm-jsonrpc.noarch 4.20.0-341.git616caa9.fc25 vdsm-python.noarch 4.20.0-341.git616caa9.fc25 vdsm-xmlrpc.noarch 4.20.0-341.git616caa9.fc25 vdsm-yajsonrpc.noarch 4.20.0-341.git616caa9.fc25 How reproducible: 100% Steps to Reproduce: ?, Try to start and shutdown a VM. Actual results: vdsmd service is stopped, host is Non-responsive in engine Expected results: vdsmd is not crashing Additional info: The host has selinux disabled