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 851413 - need clear error message when virsh connect to an invalid URI
Summary: need clear error message when virsh connect to an invalid URI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libvirt
Version: 6.4
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks: 956956
TreeView+ depends on / blocked
 
Reported: 2012-08-24 06:41 UTC by yanbing du
Modified: 2016-04-26 13:45 UTC (History)
7 users (show)

Fixed In Version: libvirt-0.10.2-31.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 956956 (view as bug list)
Environment:
Last Closed: 2014-10-14 04:14:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2014:1374 0 normal SHIPPED_LIVE libvirt bug fix and enhancement update 2014-10-14 08:11:54 UTC

Description yanbing du 2012-08-24 06:41:35 UTC 
Description of problem:
error message need improve when virsh connect to a invalid uri.

Version-Release number of selected component (if applicable):
libvirt-0.10.0-0rc1.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.# virsh connect hello
error: Failed to connect to the hypervisor
error: no connection driver available for No connection for URI hello
error: Failed to reconnect to the hypervisor
2.
3.
  
Actual results:
error: no connection driver available for No connection for URI hello

Expected results:
need correct and clear error message.

Additional info:
Comment 4 Ján Tomko 2013-02-26 14:06:06 UTC 
Fixed upstream by:
commit 633d859b7375ff33c8307addf92683bc05ac8798
Author:     Ján Tomko <jtomko>
AuthorDate: 2013-02-26 13:00:08 +0100
Commit:     Ján Tomko <jtomko>
CommitDate: 2013-02-26 15:01:03 +0100

    libvirt: fix error message when connection can't be opened
    
    VIR_ERR_NO_CONNECT already contains "no connection driver available".
    
    This patch changes:
    no connection driver available for No connection for URI hello
    to:
    no connection driver available for hello
Comment 6 tingting zheng 2013-04-26 05:33:04 UTC 
Also I tried to use virsh to connect a invalid xen uri,the error also occurs:
# virsh -c xen+ssh://10.66.72.24/system list --all
root.72.24's password: 
error: no connection driver available for No connection for URI xen:///system
error: failed to connect to the hypervisor
Comment 7 Jiri Denemark 2013-06-11 10:05:46 UTC 
We decided not to rebase libvirt in RHEL 6.5 to avoid stability issues
we faced in 6.4. This bug has already been trivially fixed upstream but
it is not considered important enough to be backported to RHEL 6.5.

Thus I'm pushing this bug to RHEL 6.6 (and setting Upstream keyword to
indicate we have patches upstream) for now. If you don't agree with
this resolution, please, give us reasons which you think are strong
enough for us to reevaluate the decision not to backport patches for
this bug.
Comment 12 yanbing du 2014-04-14 09:16:25 UTC 
# rpm -q libvirt
libvirt-0.10.2-32.el6.x86_64

# virsh connect hi
error: Failed to connect to the hypervisor
error: no connection driver available for hi
error: Failed to reconnect to the hypervisor

Move bug to VERIFIED.
Comment 14 errata-xmlrpc 2014-10-14 04:14:11 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-2014-1374.html
Note You need to log in before you can comment on or make changes to this bug.