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.
Bug 593573 - virt-manager cannot connect to remote hosts [nightly 20100518]
Summary: virt-manager cannot connect to remote hosts [nightly 20100518]
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: virt-manager
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Cole Robinson
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-19 07:54 UTC by Christopher Curran
Modified: 2010-05-20 02:00 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-19 15:37:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Christopher Curran 2010-05-19 07:54:10 UTC
Description of problem:
virt-manager cannot connect to remote hosts presently. I've tried a RHEL5 KVM host and a Fedora 12 KVM host, both report the same error. There are no issues with the connection as virsh can connect to the hypervisor and issue commands.

Version-Release number of selected component (if applicable):
RHEL6-Client-20100518

How reproducible:
RHEL5.5 and Fedora 12 report errors.

Steps to Reproduce:
1. Open virt-manager
2. Select File->'Add Connection...'
3. input the details for the host
  
Actual results:
Python error:
Unable to open connection to hypervisor URI 'qemu+ssh://root.redhat.com/system':
cannot recv data: Resource temporarily unavailable
Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 992, in _try_open
    None], flags)
  File "/usr/lib64/python2.6/site-packages/libvirt.py", line 111, in openAuth
    if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: cannot recv data: Resource temporarily unavailable

Maybe you need to install ssh-askpass in order to authenticate.


Expected results:
connection works.

Additional info:
ssh-askpass is not available in RHEL6.

Comment 2 Cole Robinson 2010-05-19 15:37:06 UTC
SSH askpass looks like it was only added to the RHEL6 repos within the past couple days :)

I can see it here:

http://qafiler.bos.redhat.com/redhat/nightly/RHEL6.0-20100519.n.1/6/Server/x86_64/os/Packages/

but not here:

http://qafiler.bos.redhat.com/redhat/nightly/RHEL6.0-20100514.n.0/6/Server/x86_64/os/Packages/

(strangley http://qafiler.bos.redhat.com/redhat/nightly/latest-RHEL6.0/ points to the old tree).

Lack of askpass is the reason you are seeing that error, so closing as WORKSFORME.

Comment 3 Christopher Curran 2010-05-20 02:00:11 UTC
Works for me too now. Verified, this is fixed.


Note You need to log in before you can comment on or make changes to this bug.