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:
I can create connection when Hypervisor is not assigned any value

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


How reproducible:
Always

Steps to Reproduce:
1. open virt manager
2. click File -> Add Connection
3. Don't select any value for Hypervisor, and click Connect
  
Actual results:
The connection can be created although it cannot be connected.

Expected results:
There should be a message to remind customer "the Hypervisor is required". Or give a default value to Hypervisor. 

Additional info:

Fixed upstream by always having a default HV selection:

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

Fixed in virt-manager-0.9.0-2.el6

verified with the following components:
libvirt-0.9.4-1.el6.x86_64
virt-manager-0.9.0-5.el6.x86_64

Steps:
1. open virt manager
2. click File -> Add Connection
Hypervisor has a default value, could not be empty.

    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