| Summary: | daily cron reports "no connection driver available for lxc:///" | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Viorel Tabara <viorel.tabara> |
| Component: | libvirt-sandbox | Assignee: | Daniel Berrangé <berrange> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 25 | CC: | andrew.kavalov, berrange, dwalsh, virt-maint |
| Target Milestone: | --- | ||
| 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-12-12 11:03:44 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: | |
I'm seeing this in Virtual Machine Manager too. I'm trying to open a new connection for LXC. I went to the "New Connection" menu and selected "LXC".
Unable to connect to libvirt.
no connection driver available for lxc:///
Libvirt URI is: lxc:///
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/connection.py", line 904, in _do_open
self._backend.open(self._do_creds_password)
File "/usr/share/virt-manager/virtinst/connection.py", line 148, in open
open_flags)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 105, in openAuth
if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: no connection driver available for lxc:///
I'm assuming I need to install some more packages or enable and start a service or both, but it's not clear how to do that.
Same here.
In addition even with selinux in Permissive mode and run as root:
virsh --connect qemu:///session
or any other virsh command like say:
virsh --debug 2 --connect qemu:///system
does absolutely nothing - with no debug or error message, or any other output.
No errors reported by libvirtd:
systemctl status libvirtd
● libvirtd.service - Virtualization daemon
Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2017-03-29 19:28:42 EDT; 2h 17min ago
Docs: man:libvirtd(8)
http://libvirt.org
Main PID: 1547 (libvirtd)
Tasks: 20 (limit: 512)
CGroup: /system.slice/libvirtd.service
├─1547 /usr/sbin/libvirtd
├─1836 /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libv
└─1915 /usr/bin/qemu-system-alpha -S -no-user-config -nodefaults -nographic -M none -qmp unix:/var/lib/libv
Mar 29 19:28:31 armat1.home systemd[1]: Starting Virtualization daemon...
Mar 29 19:28:42 armat1.home systemd[1]: Started Virtualization daemon.
Hope it helps.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |
Description of problem: /etc/cron.daily/virt-sandbox-service.logrotate errors with: error: failed to connect to the hypervisor error: no connection driver available for lxc:/// Version-Release number of selected component (if applicable): libvirt-daemon-lxc-2.2.0-1.fc25.x86_64 Mon 10 Oct 2016 03:48:30 PM MDT libvirt-sandbox-0.6.0-2.fc24.x86_64 Mon 10 Oct 2016 03:30:13 PM MDT libvirt-sandbox-libs-0.6.0-2.fc24.x86_64 Tue 04 Oct 2016 12:28:15 AM MDT libvirt-daemon-driver-lxc-2.2.0-1.fc25.x86_64 Tue 04 Oct 2016 12:28:15 AM MDT How reproducible: On every run. Steps to Reproduce: Run the cron daily script included with the package. Additional info: Following the test case at: https://fedoraproject.org/wiki/QA:Testcase_VirtSandbox_CommonSetup [root@omiday ~]# rpm -qa | grep -i lxc libvirt-daemon-lxc-2.2.0-1.fc25.x86_64 libvirt-daemon-driver-lxc-2.2.0-1.fc25.x86_64 The daemon-driver package is empty? omiday ~ $ rpm -ql --scripts --triggers libvirt-daemon-lxc (contains no files)