Bug 709303

Summary:	Autoconnect should take effect in Add Connection page of virt-manager
Product:	Red Hat Enterprise Linux 6	Reporter:	Min Zhan <mzhan>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2	CC:	dyuan, llim, mshao, mzhan, zpeng
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	No description necessary	Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-12-06 16:14:21 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Min Zhan 2011-05-31 10:29:39 UTC

Description of problem:
Launch virt-manager, Click File-> Add Connection, Create a Connection and Tick Autoconnect. But when re-open virt-manager, the connection will not auto connected.

Version-Release number of selected component (if applicable):
libvirt-0.9.1-1.el6.x86_64
virt-manager-0.8.6-4.el6.noarch

How reproducible:
Always

Steps to Reproduce:

1. Launch virt-manager

2. Click File-> Add Connection, Create a Connection and Tick Autoconnect checkbox. Such as localhost (QEMU). make sure no Autoconnect is ticked in Connection details page

3. Connection is active and with guests listed

4. Quit virt-manager and re-open virt-manager, check localhost (QEMU) can be autoconnected or not
  
Actual results:
localhost (QEMU) is disconnected

Expected results:
The connection should be autoconnected when launching virt-manager

Additional info:
1. Autoconnect take effect when ticking Autoconnect checkbox in Connection details page of virt-manager

Comment 1 Cole Robinson 2011-07-15 01:15:29 UTC

Fixed upstream:

http://git.fedorahosted.org/git?p=virt-manager.git;a=commit;h=595d3d13e724e707c69f6b6f89717d12b6b18dee

Comment 2 Cole Robinson 2011-07-28 15:29:32 UTC

Fixed in virt-manager-0.9.0-2.el6

Comment 4 zhe peng 2011-08-04 06:52:58 UTC

this bug can reproduce with virt-manager-0.8.6-4.el6.noarch

Verify with:
virt-manager-0.9.0-5.el6
libvirt-0.9.4-1.el6

step:
1. Launch virt-manager

2. Click File-> Add Connection, Create a Connection and Tick Autoconnect
checkbox. Such as localhost (QEMU). make sure no Autoconnect is ticked in
Connection details page

3. Connection is active and with guests listed

4. Quit virt-manager and re-open virt-manager
the connection will autoconnect,and Autoconnect is ticked in Connection details page automatic. so the bug fixed.
Verification passed.

Comment 5 Cole Robinson 2011-11-07 16:40:26 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No description necessary

Comment 6 errata-xmlrpc 2011-12-06 16:14:21 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1642.html