Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

Fixed upstream:

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

Fixed in virt-manager-0.9.0-2.el6

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.

    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

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