Bug 1235972

Summary:	LXC not appear in Add New Connection
Product:	[Fedora] Fedora	Reporter:	Juan Antonio Clavero García <jclaverogarcia>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	22	CC:	berrange, crobinso, jakobunt, jclaverogarcia, mbaudier, virt-maint
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	virt-manager-1.2.1-2.fc22	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-18 05:14:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Juan Antonio Clavero García 2015-06-26 08:56:39 UTC

User-Agent:       Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0
Build Identifier: 

When you try to add a new connection the ability to select not appear LXC.

The goal is to access the containers through remote connections to a computer where all the containers are. This worked correctly in FC21.

Reproducible: Always

Steps to Reproduce:
1. Open virt-manager
2. File -> add connection
LXC not appear in Hypervisor
Actual Results:  
not applicable

Expected Results:  
The ability to select LXC

They are installed:

libvirt-daemon-lxc-1.2.13.1-2.fc22.x86_64
libvirt-daemon-driver-lxc-1.2.13.1-2.fc22.x86_64
virt-manager-1.2.1-1.fc22.noarch
virt-manager-common-1.2.1-1.fc22.noarch

and others.

Comment 1 Juan Antonio Clavero García 2015-06-28 18:23:11 UTC

It is not the solution but ... Running virt-manager with --connect option runs correctly what I need, then it is a matter of marking the option to auto-connect to the details of the connection.

Comment 2 Juan Antonio Clavero García 2015-07-01 07:58:42 UTC

I have observed that the failure occurs in Gnome, Cinnamon yet working properly. I have not had chance to try it on other desktops.

After this check, I remember that there were similar bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1158515
https://bugzilla.redhat.com/show_bug.cgi?id=1183100

Comment 3 Juan Antonio Clavero García 2015-07-01 08:01:01 UTC

Sorry, the last comment is for other bugs. Please remove.

Comment 4 jakobunt 2015-08-02 10:21:38 UTC

Just to make that clear, the workaround is:

$ virt-manager --connect lxc://

then enable Autoconnect for the LXC connection. Works fine here on Fedora 22.

Comment 5 Cole Robinson 2015-08-09 22:17:02 UTC

Thanks for the report. I've added LXC to the default connection list:

commit 59b30c81a0a31c74138a6fed6ae68e79e048836a
Author: Cole Robinson <crobinso>
Date:   Sun Aug 9 18:15:37 2015 -0400

    spec: Add LXC to default connection list (bz 1235972)

Comment 6 Fedora Update System 2015-08-11 20:12:00 UTC

virt-manager-1.2.1-2.fc22 has been submitted as an update for Fedora 22.
https://admin.fedoraproject.org/updates/virt-manager-1.2.1-2.fc22

Comment 7 Fedora Update System 2015-08-13 16:53:53 UTC

Package virt-manager-1.2.1-2.fc22:
* should fix your issue,
* was pushed to the Fedora 22 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing virt-manager-1.2.1-2.fc22'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-13390/virt-manager-1.2.1-2.fc22
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2015-08-18 05:14:24 UTC

virt-manager-1.2.1-2.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Mathieu Baudier 2016-06-01 15:22:38 UTC

The problem is still there on an up-to-date CentOS 7:

Installed Packages
virt-manager.noarch                      1.2.1-8.el7                       @base